From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xenproject.org
Cc: jgross@suse.com, Lars Kurth <lars.kurth@citrix.com>,
netwiz@crc.id.au, Ian Campbell <ian.campbell@citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Jan Beulich <JBeulich@suse.com>,
wei.liu2@citrix.com, cardoe@cardoe.com
Subject: Re: RFC: LTS and stable release scheme
Date: Tue, 6 Oct 2015 14:15:10 +0100 [thread overview]
Message-ID: <20151006131510.GD29124@zion.uk.xensource.com> (raw)
In-Reply-To: <20151006110758.GV29124@zion.uk.xensource.com>
On Tue, Oct 06, 2015 at 12:07:58PM +0100, Wei Liu wrote:
> Hi all
>
> A majority of developers express interests in trying a shorter release
> cycle -- to change from 9 months to 6 months [0]. There are, however,
> repercussions on how we manage stable and possible LTS releases.
>
> I start this thread hoping it's clearer that downstream consumers like
> distributions and individual packagers can voice their opinions. I've
> CC'ed some people I can think of who might be interested in this topic.
> Feel free to CC more people.
>
> We don't have LTS scheme at the moment. Let me start with current
> scheme for stable releases.
>
> - Release from xen-unstable every 9 months.
> - Maintain last 3 releases as stable releases.
>
Important correction, according to
http://wiki.xenproject.org/wiki/Xen_Project_Maintenance_Releases
A stable release is supported fully for 18 months + 18 months security
updates.
This changes some numbers the following calculations. But I think the
premises for following discussions are still the same.
Wei.
next prev parent reply other threads:[~2015-10-06 13:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 11:07 RFC: LTS and stable release scheme Wei Liu
2015-10-06 12:57 ` George Dunlap
2015-10-06 13:10 ` Ian Campbell
2015-10-06 16:25 ` Wei Liu
2015-10-06 16:30 ` Ian Campbell
2015-10-06 13:15 ` Wei Liu [this message]
2015-10-06 13:38 ` Jan Beulich
2015-10-06 14:09 ` Wei Liu
2015-10-06 14:52 ` Jan Beulich
2015-10-06 15:01 ` Wei Liu
2015-10-07 17:45 ` George Dunlap
2015-10-08 8:05 ` Jan Beulich
2015-10-08 10:39 ` George Dunlap
2015-10-08 11:48 ` Jan Beulich
2015-10-08 10:59 ` Ian Jackson
2015-10-08 11:34 ` Jan Beulich
[not found] ` <561670CD02000078000A94AA@suse.com>
2015-10-08 11:49 ` Juergen Gross
2015-10-08 12:22 ` Jan Beulich
[not found] ` <56167C0802000078000A953E@suse.com>
2015-10-08 12:39 ` Juergen Gross
2015-10-08 13:52 ` Wei Liu
2015-10-08 11:10 ` Wei Liu
2015-10-08 12:13 ` Jan Beulich
2015-10-08 14:23 ` Wei Liu
2015-10-08 15:01 ` Jan Beulich
2015-10-08 11:10 ` George Dunlap
2015-10-06 14:12 ` George Dunlap
2015-10-06 14:49 ` Jan Beulich
2015-10-07 17:56 ` George Dunlap
2015-10-08 8:15 ` Jan Beulich
2015-10-06 15:27 ` Dario Faggioli
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=20151006131510.GD29124@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=cardoe@cardoe.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=jgross@suse.com \
--cc=lars.kurth@citrix.com \
--cc=netwiz@crc.id.au \
--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.