applying bug fixes

applying bug fixes

[Brian Hays]

[-- Attachment #1.1: Type: text/plain, Size: 241 bytes --]

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 3.0.2 is released?

Thank you,
Brian

[-- Attachment #1.2: Type: text/html, Size: 251 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: applying bug fixes

[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 3.0.2 is
> released?

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).

Ewan.

Re: applying bug fixes

[Brian Hays]

[-- Attachment #1.1: Type: text/plain, Size: 1658 bytes --]

Thank you. Is 3.0-testing now considered 3.0.2-rc? Or is that separate?

Thank you,
Brian

On 3/26/06, Ewan Mellor <ewan@xensource.com> wrote:
>
> 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 3.0.2 is
> > released?
>
> 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).
>
> Ewan.
>

[-- Attachment #1.2: Type: text/html, Size: 2001 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: applying bug fixes

[Matt Ayres]

Ewan Mellor wrote:

> 
> 3.0.2 will be about a week (we tagged 3.0.2-rc last Friday).
> 

In relation to this, should we expect another sweep into 3.0-testing or 
is the tree in bug fix only mode?  I remember 2.6.16 kernel was expected 
to be distributed with 3.0.2.

Thanks,
Matt Ayres

Re: applying bug fixes

[Anthony Liguori]

Ewan Mellor wrote:
> 3.0.2 will be about a week (we tagged 3.0.2-rc last Friday).
>   

I noticed that 3.0.2-rc was tagged on Friday.  Can you explain the 
significance of that?  Is that particular changeset going to become 
3.0.2?  Are you just doing extended testing on it or are you just going 
to tag a new changeset in a week as 3.0.2?

Regards,

Anthony Liguori

> Ewan.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>   

RE: applying bug fixes

[Ian Pratt]

> I noticed that 3.0.2-rc was tagged on Friday.  Can you 
> explain the significance of that?  Is that particular 
> changeset going to become 3.0.2?  Are you just doing extended 
> testing on it or are you just going to tag a new changeset in 
> a week as 3.0.2?

We were just going to sweep -unstable into -testing and call a 3.0.2
release, but it was felt that since there had been some significant
changes in the previous few days letting it sit in unstable for a few
days wouldn't be a bad thing. Adding the -rc tag was done to remind
patch submitters we're close to a release (bug fixes only) and to give
the testers a heads-up.

Ian 

Re: applying bug fixes

[Anthony Liguori]

Ian Pratt wrote:
>> I noticed that 3.0.2-rc was tagged on Friday.  Can you 
>> explain the significance of that?  Is that particular 
>> changeset going to become 3.0.2?  Are you just doing extended 
>> testing on it or are you just going to tag a new changeset in 
>> a week as 3.0.2?
>>     
>
> We were just going to sweep -unstable into -testing and call a 3.0.2
> release, but it was felt that since there had been some significant
> changes in the previous few days letting it sit in unstable for a few
> days wouldn't be a bad thing. Adding the -rc tag was done to remind
> patch submitters we're close to a release (bug fixes only) and to give
> the testers a heads-up.
>   

Excellent, thanks for the heads up.

Regards,

Anthony Liguori

> Ian 
>