Folks, The current plan is to release Xen 3.2.0, based on the current xen-unstable codebase, towards the end of November. To achieve that goal we need to start stabilising the tree in the next week or two. Therefore, if you have any new features to add to the tree, please post patches in the next week or send email to the list describing your expected schedule for patch release. I expect to freeze the tree within a fortnight, from which point I will accept bug fixes only. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Daniel P. Berrange
2007-Oct-12 15:40 UTC
Re: [Xen-devel] Stabilising xen-unstable for 3.2.0
On Fri, Oct 12, 2007 at 04:29:51PM +0100, Keir Fraser wrote:> Folks, > > The current plan is to release Xen 3.2.0, based on the current xen-unstable > codebase, towards the end of November. To achieve that goal we need to start > stabilising the tree in the next week or two. Therefore, if you have any new > features to add to the tree, please post patches in the next week or send > email to the list describing your expected schedule for patch release. I > expect to freeze the tree within a fortnight, from which point I will accept > bug fixes only.FYI, I intend to re-submit the paravirt framebuffer -> QEMU merge patches again as soon as I''ve re-verified save/restore against current xen-unstable Regards, Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=| _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 12/10/07 16:40, "Daniel P. Berrange" <berrange@redhat.com> wrote:>> The current plan is to release Xen 3.2.0, based on the current xen-unstable >> codebase, towards the end of November. To achieve that goal we need to start >> stabilising the tree in the next week or two. Therefore, if you have any new >> features to add to the tree, please post patches in the next week or send >> email to the list describing your expected schedule for patch release. I >> expect to freeze the tree within a fortnight, from which point I will accept >> bug fixes only. > > FYI, I intend to re-submit the paravirt framebuffer -> QEMU merge patches > again as soon as I''ve re-verified save/restore against current xen-unstableSounds like they should be ready within the next week or two, which is absolutely fine. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel