From: Ian Campbell <ian.campbell@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
tim@xen.org, keir@xen.org
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Lars Kurth <lars.kurth@citrix.com>
Subject: Re: [VOTE] Release cycle scheme
Date: Wed, 4 Nov 2015 11:32:21 +0000 [thread overview]
Message-ID: <1446636741.6461.73.camel@citrix.com> (raw)
In-Reply-To: <20151102134721.GC18337@zion.uk.xensource.com>
On Mon, 2015-11-02 at 13:47 +0000, Wei Liu wrote:
>
> So I propose we use the following scheme:
>
> - 6 months release cycle from unstable branch.
> - 4 months development.
> - 2 months freeze.
+1
> - 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.
+2
> - No more freeze exception, but heads-up mails about freeze will be
> sent a few weeks before hand.
+2
> - Stable branch maintained for 18 months full support plus 18 months
> security support. No mixed maintainership for stable trees.
0.
> Please vote to ack or nack this proposal.
Overall +1. I just wanted to highlight the three aspects which really
matter IMHO (although I agree with George that the "Fixed..." and "No
more..." are really up to the RM to decide).
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-11-04 11:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 13:47 [VOTE] Release cycle scheme Wei Liu
2015-11-04 8:53 ` Lars Kurth
2015-11-04 9:59 ` George Dunlap
2015-11-04 10:46 ` Jan Beulich
2015-11-09 11:04 ` Wei Liu
2015-11-09 11:24 ` Lars Kurth
2015-11-09 11:50 ` Wei Liu
2015-11-09 11:56 ` Lars Kurth
2015-11-04 11:32 ` Ian Campbell [this message]
2015-11-04 12:27 ` Ian Jackson
2015-11-05 13:56 ` Stefano Stabellini
2015-11-05 15:40 ` Tim Deegan
2015-11-05 20:58 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446636741.6461.73.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=konrad.wilk@oracle.com \
--cc=lars.kurth@citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.