It seems like it has been quite a while since our last stable branch releases. Shall we try and get 4.0.4 and 4.1.3 out of the way before we get too deep into the 4.2 release closedown? Perhaps we could do a first rc of each in the next few weeks? Ian.
On 11/04/2012 18:07, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:> It seems like it has been quite a while since our last stable branch > releases. > > Shall we try and get 4.0.4 and 4.1.3 out of the way before we get too > deep into the 4.2 release closedown? > > Perhaps we could do a first rc of each in the next few weeks?Yes, it''s about time. -- Keir> Ian. >
On Wed, 11 Apr 2012, Ian Campbell wrote:> It seems like it has been quite a while since our last stable branch > releases. > > Shall we try and get 4.0.4 and 4.1.3 out of the way before we get too > deep into the 4.2 release closedown? > > Perhaps we could do a first rc of each in the next few weeks?I am keen on having these three patches in 4.1.3: http://marc.info/?l=xen-devel&m=133251438030441 I asked Ian to backport them in a previous email.
On 04/11/2012 01:41 PM, Keir Fraser wrote:> On 11/04/2012 18:07, "Ian Campbell"<Ian.Campbell@citrix.com> wrote: > >> It seems like it has been quite a while since our last stable branch >> releases. >> >> Shall we try and get 4.0.4 and 4.1.3 out of the way before we get too >> deep into the 4.2 release closedown? >> >> Perhaps we could do a first rc of each in the next few weeks? > Yes, it''s about time.Before tagging 4.1.3, may I request the following changesets backported from xen-unstable? Will you consider them? -Wei ==== SVM Decode Assist ===changeset 23233:1276926e3795 changeset 23234:bf7afd48339a changeset 23235:2c8ad607ece1 changeset 23236:e324c4d1dd6e changeset 23237:381ab77db71a changeset 23238:60f5df2afcbb ==== SVM TSC Scaling ===changeset 23437:d7c755c25bb9 ==== Performance Monitor Counters ===changeset 23304:8981b582be3e changeset 23305:014ee4e09644 changeset 23306:e787d4f2e5ac> > -- Keir > >> Ian. >> > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel >
On 12/04/2012 00:11, "Wei Huang" <wei.huang2@amd.com> wrote:> On 04/11/2012 01:41 PM, Keir Fraser wrote: >> On 11/04/2012 18:07, "Ian Campbell"<Ian.Campbell@citrix.com> wrote: >> >>> It seems like it has been quite a while since our last stable branch >>> releases. >>> >>> Shall we try and get 4.0.4 and 4.1.3 out of the way before we get too >>> deep into the 4.2 release closedown? >>> >>> Perhaps we could do a first rc of each in the next few weeks? >> Yes, it''s about time. > Before tagging 4.1.3, may I request the following changesets backported > from xen-unstable? Will you consider them?Done. -- Keir> -Wei > > ==== SVM Decode Assist ===> changeset 23233:1276926e3795 > changeset 23234:bf7afd48339a > changeset 23235:2c8ad607ece1 > changeset 23236:e324c4d1dd6e > changeset 23237:381ab77db71a > changeset 23238:60f5df2afcbb > > ==== SVM TSC Scaling ===> changeset 23437:d7c755c25bb9 > > ==== Performance Monitor Counters ===> changeset 23304:8981b582be3e > changeset 23305:014ee4e09644 > changeset 23306:e787d4f2e5ac > > > >> >> -- Keir >> >>> Ian. >>> >> >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xen.org >> http://lists.xen.org/xen-devel >> > >
Stefano Stabellini writes ("Re: [Xen-devel] Stable branch
releases?"):> I am keen on having these three patches in 4.1.3:
> http://marc.info/?l=xen-devel&m=133251438030441
>
> I asked Ian to backport them in a previous email.
Right.
The first step in making a stable branch release should be to send a
message to xen-devel asking for people to resend any outstanding
backport requests, and setting a deadline for responses.
Ian.
On Thu, 2012-04-12 at 11:47 +0100, Ian Jackson wrote:> Stefano Stabellini writes ("Re: [Xen-devel] Stable branch releases?"): > > I am keen on having these three patches in 4.1.3: > > http://marc.info/?l=xen-devel&m=133251438030441 > > > > I asked Ian to backport them in a previous email. > > Right. > > The first step in making a stable branch release should be to send a > message to xen-devel asking for people to resend any outstanding > backport requests, and setting a deadline for responses.Shall we say a deadline of a week tomorrow (Friday 20th)? Does this thread suffice as the request? Ian.
On 12/04/2012 15:59, "Ian Campbell" <Ian.Campbell@citrix.com> wrote:> On Thu, 2012-04-12 at 11:47 +0100, Ian Jackson wrote: >> Stefano Stabellini writes ("Re: [Xen-devel] Stable branch releases?"): >>> I am keen on having these three patches in 4.1.3: >>> http://marc.info/?l=xen-devel&m=133251438030441 >>> >>> I asked Ian to backport them in a previous email. >> >> Right. >> >> The first step in making a stable branch release should be to send a >> message to xen-devel asking for people to resend any outstanding >> backport requests, and setting a deadline for responses. > > Shall we say a deadline of a week tomorrow (Friday 20th)? > > Does this thread suffice as the request?Make a new thread with a very explicit subject line, with [ANNOUNCE] or similar in it. -- Keir> Ian. >
On Thu, 2012-04-12 at 17:04 +0100, Keir Fraser wrote:> On 12/04/2012 15:59, "Ian Campbell" <Ian.Campbell@citrix.com> wrote: > > > On Thu, 2012-04-12 at 11:47 +0100, Ian Jackson wrote: > >> Stefano Stabellini writes ("Re: [Xen-devel] Stable branch releases?"): > >>> I am keen on having these three patches in 4.1.3: > >>> http://marc.info/?l=xen-devel&m=133251438030441 > >>> > >>> I asked Ian to backport them in a previous email. > >> > >> Right. > >> > >> The first step in making a stable branch release should be to send a > >> message to xen-devel asking for people to resend any outstanding > >> backport requests, and setting a deadline for responses. > > > > Shall we say a deadline of a week tomorrow (Friday 20th)? > > > > Does this thread suffice as the request? > > Make a new thread with a very explicit subject line, with [ANNOUNCE] or > similar in it.Done.