xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz@crc.id.au>
To: xen-devel@lists.xen.org
Subject: Re: RFC: change to 6 months release cycle
Date: Mon, 5 Oct 2015 22:44:30 +1100	[thread overview]
Message-ID: <5612629E.8020003@crc.id.au> (raw)
In-Reply-To: <20151005112357.GC29124@zion.uk.xensource.com>


[-- Attachment #1.1: Type: text/plain, Size: 2076 bytes --]

On 5/10/2015 10:23 PM, Wei Liu wrote:
> On Mon, Oct 05, 2015 at 05:04:19AM -0600, Jan Beulich wrote:
>>>>> On 02.10.15 at 19:43, <wei.liu2@citrix.com> wrote:
>>> The main objection from previous discussion seems to be that "shorter
>>> release cycle creates burdens for downstream projects". I couldn't
>>> quite get the idea, but I think we can figure out a way to sort that
>>> out once we know what exactly the burdens are.
>>
>> I don't recall it that way. My main objection remains the resulting
>> higher burden of maintaining stable trees. Right now, most of the
>> time we have two trees to maintain. A 6-month release cycle means
>> three of them (shortening the time we maintain those trees doesn't
>> seem a viable option to me).
>>
>> Similar considerations apply to security maintenance of older trees.
<snip>
> Just to throw around some ideas: we can have more stable tree
> maintainers, we can pick a stable tree every X releases etc etc.

So everyone else in the industry is increasing their support periods for
stable things, and we're wanting to go the opposite way?

Sorry - but this is nuts. Have a stable branch that is actually
supported properly with backports of security fixes etc - then have a
'bleeding edge' branch that rolls with the punches.

Remember that folks are still running Xen 3.4 on EL5 - and will be at
least until 2017. I still run the occasional patch for 4.2, and most
people are on either 4.4 or testing with 4.5 when running with EL6.

EL6 is supported until November 30, 2020. EL7 until 2024. People are not
exactly thrilled with EL7 in the virt area - but will eventually move to
it (or directly to EL8 or EL9).

The 6 month release cycle is exactly why people don't run Fedora on
their production environments. Why are we suddenly wanting the same
release schedule for Xen?

Sorry - but I'm VERY much against this proposal. Focus on stable and
complete, not Ooohhhh Shiny!

-- 
Steven Haigh

Email: netwiz@crc.id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  parent reply	other threads:[~2015-10-05 11:44 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 [this message]
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=5612629E.8020003@crc.id.au \
    --to=netwiz@crc.id.au \
    --cc=xen-devel@lists.xen.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).