[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [VOTE] Release cycle scheme
Wei Liu writes ("[VOTE] Release cycle scheme"): > There are comments made by individuals that couldn't be clearly > represent in tally. The most acceptable option to stable tree > maintainers is #1. > > So I propose we use the following scheme: +1 Following Ian Campbell's lead, I want to comment on the aspects of the proposal: > - 6 months release cycle from unstable branch. +2 > - 4 months development. > - 2 months freeze. > - Eat into next cycle if doesn't release on time. +2 > - Fixed cut-off date: the Fridays of the week in which the last day of > March and September falls. +1 You should perhaps adjust the wording here because the ends of a "week" are slightly fuzzy. How about "the last Friday in March or September" ? (With my own definition of "week", which has weeks running Sunday to Saturday, I think what you wrote means the same as "the Friday after the last Sunday in March or September" - which is rather complex!) > - No more freeze exception, but heads-up mails about freeze will be > sent a few weeks before hand. 0 > - Stable branch maintained for 18 months full support plus 18 months > security support. No mixed maintainership for stable trees. +1 Ian. _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |