From: Dario Faggioli <dario.faggioli@citrix.com>
To: Wei Liu <wei.liu2@citrix.com>, xen-devel@lists.xenproject.org
Cc: Lars Kurth <lars.kurth@citrix.com>
Subject: Re: RFC: change to 6 months release cycle
Date: Sat, 3 Oct 2015 03:04:31 +0200 [thread overview]
Message-ID: <1443834271.14525.96.camel@citrix.com> (raw)
In-Reply-To: <20151002174356.GA3577@zion.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1349 bytes --]
On Fri, 2015-10-02 at 18:43 +0100, Wei Liu wrote:
> # Proposed release cycle
>
> Aim for 6 months release cycle -- 4 months development period, 2
> months hardening period. Make two releases per year.
>
> Fixed hard cut-off date, no more freeze exception. Arrange RCs
> immediately after cut-off.
>
> Take into account holiday seasons in US, Europe and China, the two
> cut-off dates are the Fridays in which that last day of March and
> September are in.
> Comments are welcome!
>
+1
I do like a lot the fact that this, as Wei mentioned, gives us the
chance to (at least potentially) deliver new features and improvements
much faster/more frequent to downstreams and end users.
Also, I think the idea of code and feature freeze, with freeze
exceptions, was a good idea, and served us well for the first couple of
releases for which it's been in effect. However, lately, maybe also
because of changes/evolution of the project and the community, it has
IMO shown its limits, and did cause issues, so I'd really love ditching
that.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-10-03 1:04 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 17:43 RFC: change to 6 months release cycle Wei Liu
2015-10-02 17:52 ` Juergen Gross
2015-10-02 18:21 ` Andrew Cooper
2015-10-05 9:45 ` Ian Campbell
2015-10-05 10:01 ` Juergen Gross
2015-10-06 15:22 ` Stefano Stabellini
2015-10-02 18:17 ` Andrew Cooper
2015-10-03 1:04 ` Dario Faggioli [this message]
2015-10-05 9:55 ` Ian Campbell
2015-10-05 10:19 ` Wei Liu
2015-10-05 10:29 ` George Dunlap
2015-10-05 10:42 ` Wei Liu
2015-10-05 11:04 ` Jan Beulich
2015-10-05 11:23 ` Wei Liu
2015-10-05 11:37 ` Jan Beulich
2015-10-05 12:52 ` Wei Liu
2015-10-05 13:31 ` Jan Beulich
2015-10-05 13:51 ` Wei Liu
2015-10-05 14:07 ` Jan Beulich
2015-10-05 14:50 ` Wei Liu
2015-10-05 15:08 ` Jan Beulich
2015-10-05 11:44 ` Steven Haigh
2015-10-05 13:05 ` Wei Liu
2015-10-05 13:05 ` George Dunlap
2015-10-05 13:21 ` Steven Haigh
2015-10-05 16:22 ` Wei Liu
2015-10-06 13:03 ` Jan Beulich
2015-10-06 13:12 ` Wei Liu
2015-10-05 11:44 ` Ian Campbell
2015-10-05 11:51 ` Juergen Gross
2015-10-05 11:55 ` Ian Campbell
2015-10-05 12:55 ` Wei Liu
2015-10-05 13:51 ` Juergen Gross
2015-10-05 14:30 ` Wei Liu
2015-10-05 11:51 ` Steven Haigh
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=1443834271.14525.96.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=lars.kurth@citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).