[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] applying bug fixes
- To: "Ewan Mellor" <ewan@xxxxxxxxxxxxx>
- From: "Brian Hays" <brian.hays@xxxxxxxxx>
- Date: Sun, 26 Mar 2006 15:18:22 -0500
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
- Delivery-date: Sun, 26 Mar 2006 20:19:50 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=pcciaKAI2h8HJDqkDKQ2Tj+XRYFvJT2js1eCTwcEBH+osMTm3/ZBiWcTHRoQZI43K+7lXHLaKLefQG5jveVme0P1TS8rGS/vxL2m3hU+UwhT7U/OHJPZJdAG6dCaWTrn3MtsYSNmx4rhAjoK8T2AEDZ2PJ3vms3hAWk1XD9I7IA=
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
Thank you. Is 3.0-testing now considered 3.0.2-rc? Or is that separate?
On 3/26/06, Ewan Mellor <
On Sun, Mar 26, 2006 at 01:03:37PM -0500, Brian Hays wrote:
> When bug fixes occur (such as the fix for bug #514) is there any way to
> apply that fix to a stable branch (such as 3.0.1) or does it require
> either the installation of xen-unstable or waiting until
Pulling bug fixes from unstable into 3.0-testing is a manual operation,
something that one of the XenSource employees does as and when it is
needed (and preferably in batches, because it's thankless work).
If you would like to see a bug fix in 3.0-testing, then you should ask on the
list, specifying xen-unstable changesets, preferably. We will assess
the bug to determine whether the fix is risky (i.e. likely to
destabilise the stable tree) versus the impact of the bug before we
decide whether it's going to go in. If you could provide that
assessment for us, that would help too. Finally, if the patch does not
apply cleanly against unstable, then it would help if you provided a
patch that was rebased against 3.0-testing.
For each 3.0.x release, we normally sweep the whole of unstable into the
3.0-testing tree, so all bug fixes get taken at that point. You only
need to go through this arduous process for the 8 weeks or so between
releases -- any time close to a 3.0.x release, it's probably easier for
all involved just to wait for that release.
3.0.2 will be about a week (we tagged 3.0.2-rc last Friday).
Xen-devel mailing list