All of lore.kernel.org
 help / color / mirror / Atom feed
From: Agostino Sarubbo <ago@gentoo.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: security bugs and release
Date: Wed, 26 Jun 2013 17:24 +0200	[thread overview]
Message-ID: <1739559.2FeUMdQsO2@devil> (raw)
In-Reply-To: <1372238494.18901.124.camel@zakaz.uk.xensource.com>

On Wednesday 26 June 2013 10:21:34 Ian Campbell wrote:
> A new point release will rollup all the applicable security updates
> issued before that point.
> 
> In addition all of our releases are tagged in version control, so you
> can trivially find out what went into it.
> 
> You could also just run the latest stable-X.Y branch from xen.git. I
> wouldn't personally recommend doing so in production but it seems to be
> a good fit for your requirements.
I'm not a xen user. I manage and coordinate the security bugs on Gentoo Linux.

> 
> > Is there a real reason because you don't make a new release?
> 
> People who deploy and run production systems want a timely, targeted and
> low risk fix for a security issue, which they can be confident of
> deploying quickly, with a minimum of disruption to their service and
> with the lowest possible chance of breakage. A new release would
> necessarily contain other fixes not related to the security issue and
> therefore takes longer to produce and longer to test and deploy in order
> to reach the same level of confidence.
> 
> I think you will find that this approach to security support is quite
> common, especially among critical system components.

Yes, in case of package like xen, should be a risk update without have done a 
better test on e.g. another test machine.


Pasi in his mail made a great proposal. I'd like if you considerate it.
-- 
Agostino Sarubbo
Gentoo Linux Developer

      parent reply	other threads:[~2013-06-26 15:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-25 17:07 security bugs and release Agostino Sarubbo
2013-06-25 23:09 ` Andrew Cooper
2013-06-25 23:56   ` Agostino Sarubbo
2013-06-26  9:21 ` Ian Campbell
2013-06-26 13:54   ` Pasi Kärkkäinen
2013-06-26 15:21     ` Agostino Sarubbo
2013-06-26 15:24   ` Agostino Sarubbo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1739559.2FeUMdQsO2@devil \
    --to=ago@gentoo.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.