All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	Jan Beulich <JBeulich@suse.com>
Cc: Lars Kurth <lars.kurth@citrix.com>, xen-devel@lists.xenproject.org
Subject: Re: RFC: change to 6 months release cycle
Date: Mon, 5 Oct 2015 12:55:00 +0100	[thread overview]
Message-ID: <1444046100.11707.196.camel@citrix.com> (raw)
In-Reply-To: <5612642A.30407@suse.com>

On Mon, 2015-10-05 at 13:51 +0200, Juergen Gross wrote:
> On 10/05/2015 01:44 PM, Ian Campbell wrote:
> > On Mon, 2015-10-05 at 12:23 +0100, Wei Liu wrote:
> > > we can pick a stable tree every X releases etc etc.
> > 
> > I think switching to an LTS style model, i.e. only supporting 1/N for
> > longer than it takes to release the next major version might be
> > interesting
> > to consider. I'm thinking e.g. of N=4 with a 6 month cycle.
> > 
> > I think some of our downstreams (i.e. distros) would like this, since
> > it
> > gives them releases which are supported for a length of time more like
> > their own release cycles.
> 
> And again there will be a rush to get a feature in at the end of each
> Nth cycle, as it will end up in the long-term stable version...

I actually think there is plenty of stuff which people just want in _some_
release.

> > On a completely different tack, one way of looking at this is that
> > there
> > are 2 releases in a given 18 month period with 9 month cycle vs 4 in
> > the 6
> 
> Huh?
> 
> 4 * 6 = 24, not 18!

Oops yes. 3*6=18 just makes my point more valid though I think.

Ian.

  reply	other threads:[~2015-10-05 11: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
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 [this message]
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=1444046100.11707.196.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=jgross@suse.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.