Folks, It''s time to start thinking about the release schedule for Xen 4.1. My proposal is to freeze the tree for new features at the start of January, and start spinning release candidates asap after that, when we are comfortable with the stability of the tree. Release should be around 6 weeks after code freeze (i.e., we aim for mid-Feb release, or end of Feb at the latest). This isn''t set in stone yet of course. Opinions welcome! -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Tue, Nov 23, 2010 at 02:44:37PM +0000, Keir Fraser wrote:> Folks, > > It''s time to start thinking about the release schedule for Xen 4.1. My > proposal is to freeze the tree for new features at the start of January, and > start spinning release candidates asap after that, when we are comfortable > with the stability of the tree. Release should be around 6 weeks after code > freeze (i.e., we aim for mid-Feb release, or end of Feb at the latest). > > This isn''t set in stone yet of course. Opinions welcome! >Related question: What''s the Xen 4.0.2 schedule? -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 23/11/2010 19:01, "Pasi Kärkkäinen" <pasik@iki.fi> wrote:>> It''s time to start thinking about the release schedule for Xen 4.1. My >> proposal is to freeze the tree for new features at the start of January, and >> start spinning release candidates asap after that, when we are comfortable >> with the stability of the tree. Release should be around 6 weeks after code >> freeze (i.e., we aim for mid-Feb release, or end of Feb at the latest). >> >> This isn''t set in stone yet of course. Opinions welcome! >> > > Related question: What''s the Xen 4.0.2 schedule?Could start spinning RCs for that now I guess. K. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser writes ("[Xen-devel] Release plan for 4.1"):> It''s time to start thinking about the release schedule for Xen 4.1. My > proposal is to freeze the tree for new features at the start of January, and > start spinning release candidates asap after that, when we are comfortable > with the stability of the tree. Release should be around 6 weeks after code > freeze (i.e., we aim for mid-Feb release, or end of Feb at the latest). > > This isn''t set in stone yet of course. Opinions welcome!Can I suggest we stop accepting "big new features" a bit earlier ? Also, we should be more careful than we have in the past about accepting many and big changes into late RCs even if they are allegedly bugfixes. So I would say, for example, as a rule not to accept fixes for non-release-critical bugs after the end of February. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Thu, Nov 25, 2010 at 07:15:54PM +0000, Ian Jackson wrote:> Keir Fraser writes ("[Xen-devel] Release plan for 4.1"): > > It''s time to start thinking about the release schedule for Xen 4.1. My > > proposal is to freeze the tree for new features at the start of January, and > > start spinning release candidates asap after that, when we are comfortable > > with the stability of the tree. Release should be around 6 weeks after code > > freeze (i.e., we aim for mid-Feb release, or end of Feb at the latest). > > > > This isn''t set in stone yet of course. Opinions welcome! > > Can I suggest we stop accepting "big new features" a bit earlier ? > > Also, we should be more careful than we have in the past about > accepting many and big changes into late RCs even if they are > allegedly bugfixes. > > So I would say, for example, as a rule not to accept fixes for > non-release-critical bugs after the end of February.^^^^^^^^ I guess you meant to write January.. ? -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen writes ("Re: [Xen-devel] Release plan for 4.1"):> On Thu, Nov 25, 2010 at 07:15:54PM +0000, Ian Jackson wrote: > > So I would say, for example, as a rule not to accept fixes for > > non-release-critical bugs after the end of February. > ^^^^^^^^ > > I guess you meant to write January.. ?Yes, well spotted :-). Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi! How to git the xen-4.0.2-rc1? Thanks! Thiago On 23 November 2010 18:10, Keir Fraser <keir@xen.org> wrote:> On 23/11/2010 19:01, "Pasi Kärkkäinen" <pasik@iki.fi> wrote: > > >> It''s time to start thinking about the release schedule for Xen 4.1. My > >> proposal is to freeze the tree for new features at the start of January, > and > >> start spinning release candidates asap after that, when we are > comfortable > >> with the stability of the tree. Release should be around 6 weeks after > code > >> freeze (i.e., we aim for mid-Feb release, or end of Feb at the latest). > >> > >> This isn''t set in stone yet of course. Opinions welcome! > >> > > > > Related question: What''s the Xen 4.0.2 schedule? > > Could start spinning RCs for that now I guess. > > K. > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Mon, Dec 06, 2010 at 07:24:57PM -0200, Martinx - ?$B%8%''!<%`%: wrote:> Hi! > > How to git the xen-4.0.2-rc1? >Xen is not developed in git, instead xen uses mercurial (hg). Xen 4.0.2-rc1-pre is available from http://xenbits.xen.org/xen-4.0-testing.hg More info/links here: http://wiki.xen.org/xenwiki/XenRepositories -- Pasi> Thanks! > Thiago > > On 23 November 2010 18:10, Keir Fraser <[1]keir@xen.org> wrote: > > On 23/11/2010 19:01, "Pasi Kärkkäinen" <[2]pasik@iki.fi> wrote: > > >> It''s time to start thinking about the release schedule for Xen 4.1. > My > >> proposal is to freeze the tree for new features at the start of > January, and > >> start spinning release candidates asap after that, when we are > comfortable > >> with the stability of the tree. Release should be around 6 weeks > after code > >> freeze (i.e., we aim for mid-Feb release, or end of Feb at the > latest). > >> > >> This isn''t set in stone yet of course. Opinions welcome! > >> > > > > Related question: What''s the Xen 4.0.2 schedule? > > Could start spinning RCs for that now I guess. > K. > > _______________________________________________ > Xen-devel mailing list > [3]Xen-devel@lists.xensource.com > [4]http://lists.xensource.com/xen-devel > > References > > Visible links > 1. mailto:keir@xen.org > 2. mailto:pasik@iki.fi > 3. mailto:Xen-devel@lists.xensource.com > 4. http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hi! I read the page http://wiki.xen.org/xenwiki/XenRepositories but I don''t see the "hg" line to get the tagged 4.0.2-rcX version... Can you help me?! Thanks! Thiago On 6 December 2010 19:34, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Mon, Dec 06, 2010 at 07:24:57PM -0200, Martinx - ?$B%8%''!<%`%: wrote: > > Hi! > > > > How to git the xen-4.0.2-rc1? > > > > Xen is not developed in git, instead xen uses mercurial (hg). > Xen 4.0.2-rc1-pre is available from > http://xenbits.xen.org/xen-4.0-testing.hg > > More info/links here: http://wiki.xen.org/xenwiki/XenRepositories > > -- Pasi > > > Thanks! > > Thiago > > > > On 23 November 2010 18:10, Keir Fraser <[1]keir@xen.org> wrote: > > > > On 23/11/2010 19:01, "Pasi Kärkkäinen" <[2]pasik@iki.fi> wrote: > > > > >> It''s time to start thinking about the release schedule for Xen > 4.1. > > My > > >> proposal is to freeze the tree for new features at the start of > > January, and > > >> start spinning release candidates asap after that, when we are > > comfortable > > >> with the stability of the tree. Release should be around 6 weeks > > after code > > >> freeze (i.e., we aim for mid-Feb release, or end of Feb at the > > latest). > > >> > > >> This isn''t set in stone yet of course. Opinions welcome! > > >> > > > > > > Related question: What''s the Xen 4.0.2 schedule? > > > > Could start spinning RCs for that now I guess. > > K. > > > > _______________________________________________ > > Xen-devel mailing list > > [3]Xen-devel@lists.xensource.com > > [4]http://lists.xensource.com/xen-devel > > > > References > > > > Visible links > > 1. mailto:keir@xen.org > > 2. mailto:pasik@iki.fi > > 3. mailto:Xen-devel@lists.xensource.com > > 4. http://lists.xensource.com/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Fri, Dec 10, 2010 at 07:04:01PM -0200, Martinx - ?$B%8%''!<%`%: wrote:> Hi! > > I read the page [1]http://wiki.xen.org/xenwiki/XenRepositories but I > don''t see the "hg" line to get the tagged 4.0.2-rcX version... > Can you help me?! >http://wiki.xen.org/xenwiki/Xen4.0 hg clone -r RELEASE-4.0.1 http://xenbits.xen.org/xen-4.0-testing.hg 4.0.2-rc1 is not yet tagged, so just get the latest head of xen-4.0-testing.hg -- Pasi> Thanks! > Thiago > > On 6 December 2010 19:34, Pasi Kärkkäinen <[2]pasik@iki.fi> wrote: > > On Mon, Dec 06, 2010 at 07:24:57PM -0200, Martinx - ?$B%8%''!<%`%: wrote: > > Hi! > > > > How to git the xen-4.0.2-rc1? > > > > Xen is not developed in git, instead xen uses mercurial (hg). > Xen 4.0.2-rc1-pre is available from > [3]http://xenbits.xen.org/xen-4.0-testing.hg > > More info/links here: [4]http://wiki.xen.org/xenwiki/XenRepositories > > -- Pasi > > > Thanks! > > Thiago > > > > On 23 November 2010 18:10, Keir Fraser <[1][5]keir@xen.org> wrote: > > > > On 23/11/2010 19:01, "Pasi Kärkkäinen" <[2][6]pasik@iki.fi> > wrote: > > > > >> It''s time to start thinking about the release schedule for Xen > 4.1. > > My > > >> proposal is to freeze the tree for new features at the start > of > > January, and > > >> start spinning release candidates asap after that, when we are > > comfortable > > >> with the stability of the tree. Release should be around 6 > weeks > > after code > > >> freeze (i.e., we aim for mid-Feb release, or end of Feb at the > > latest). > > >> > > >> This isn''t set in stone yet of course. Opinions welcome! > > >> > > > > > > Related question: What''s the Xen 4.0.2 schedule? > > > > Could start spinning RCs for that now I guess. > > K. > > > > _______________________________________________ > > Xen-devel mailing list > > [3][7]Xen-devel@lists.xensource.com > > [4][8]http://lists.xensource.com/xen-devel > > > > References > > > > Visible links > > 1. mailto:[9]keir@xen.org > > 2. mailto:[10]pasik@iki.fi > > 3. mailto:[11]Xen-devel@lists.xensource.com > > 4. [12]http://lists.xensource.com/xen-devel > > References > > Visible links > 1. http://wiki.xen.org/xenwiki/XenRepositories > 2. mailto:pasik@iki.fi > 3. http://xenbits.xen.org/xen-4.0-testing.hg > 4. http://wiki.xen.org/xenwiki/XenRepositories > 5. mailto:keir@xen.org > 6. mailto:pasik@iki.fi > 7. mailto:Xen-devel@lists.xensource.com > 8. http://lists.xensource.com/xen-devel > 9. mailto:keir@xen.org > 10. mailto:pasik@iki.fi > 11. mailto:Xen-devel@lists.xensource.com > 12. http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel