All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@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: Mon, 5 Oct 2015 10:55:37 +0100	[thread overview]
Message-ID: <1444038937.11707.181.camel@citrix.com> (raw)
In-Reply-To: <20151002174356.GA3577@zion.uk.xensource.com>

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.

+1

> 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.

I can't actually parse(*) this but +1 to the concept of having a well
established rule based on absolute times rather than relative to some
previous event.

> Targeted release date is two months after cut-off date. Still, we pick
> a Friday using the same rule. We can also release a bit earlier if
> everything goes well. If we somehow fail to release on time, we eat
> into next development cycle. The next cut-off date will still be
> fixed.

+1, I think this is a very important difference to the current scheme,
where slippage pushes out the next release, leading to uncertainty in
general and annoying things like slowly shifting the release schedule into
clashing with all sorts of things (Xmas, Chinese New Year, etc).

Ian.

(*) I think there may be a missing "of the week", i.e. "the Fridays of the
week in which the last day of March and September falls"? Anyway, I don't
actually care what the rule is, just that it exists ;-)

  parent reply	other threads:[~2015-10-05  9:55 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
2015-10-05  9:55 ` Ian Campbell [this message]
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=1444038937.11707.181.camel@citrix.com \
    --to=ian.campbell@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 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.