[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:


Following Ian Campbell's lead, I want to comment on the aspects of the

> - 6 months release cycle from unstable branch.


>   - 4 months development.
>   - 2 months freeze.
>   - Eat into next cycle if doesn't release on time.


> - Fixed cut-off date: the Fridays of the week in which the last day of
>   March and September falls.


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.


> - Stable branch maintained for 18 months full support plus 18 months
>   security support. No mixed maintainership for stable trees.



Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.