All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Steven Haigh <netwiz@crc.id.au>,
	wei.liu2@citrix.com, xen-devel@lists.xen.org
Subject: Re: RFC: change to 6 months release cycle
Date: Tue, 6 Oct 2015 14:12:26 +0100	[thread overview]
Message-ID: <20151006131226.GC29124@zion.uk.xensource.com> (raw)
In-Reply-To: <5613E2C002000078000A88E1@prv-mh.provo.novell.com>

On Tue, Oct 06, 2015 at 07:03:28AM -0600, Jan Beulich wrote:
> >>> On 05.10.15 at 18:22, <wei.liu2@citrix.com> wrote:
> > FWIW current scheme (last 3 releases as stable releases) means a release
> > is supported for at least 27 months (well, let's forget about the
> > possibility of releasing a version earlier than expected for now because
> > it never happened before).
> 
> Where did you find that? My understanding of the current scheme is
> that we generally support branches for 18 months (plus another 18
> security-only), which normally results in a wrap up release on the
> oldest maintained branch once its second successor went out.
> 

I was going to say I saw that in 
http://wiki.xenproject.org/wiki/Xen_Project_Maintenance_Releases
but it turned out I misremembered.

Now you point out this is wrong.  Thanks for correcting.

So the correct term is:

Stable releases are supported fully for 18 months plus another 18 months
of security update.

I will need to rectify the other email I send.

Wei.


> Jan

  reply	other threads:[~2015-10-06 13:12 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 [this message]
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=20151006131226.GC29124@zion.uk.xensource.com \
    --to=wei.liu2@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=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 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.