xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>, WeiLiu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Lars Kurth <lars.kurth@xen.org>
Subject: Re: Which trees are supported (Was: Re: [qemu-upstream-4.2-testing test] 77180: regressions - FAIL)
Date: Thu, 7 Jan 2016 12:00:58 +0000	[thread overview]
Message-ID: <1452168058.21055.203.camel@citrix.com> (raw)
In-Reply-To: <568E5DF902000078000C4542@prv-mh.provo.novell.com>

On Thu, 2016-01-07 at 04:45 -0700, Jan Beulich wrote:
> > > > On 07.01.16 at 12:22, <ian.campbell@citrix.com> wrote:
> > So this arose because Stefano was unaware that 4.2 was no longer
> > supported.
> > Neither am I ever confident about where the cut-off lie, e.g. I always
> > have
> > to ask if I am doing backports for a security issue.
> > 
> > We should add rows to http://wiki.xen.org/wiki/Xen_Release_Features
> > right
> > under Initial Release giving first the date until which that tree is
> > supported with backports and second the date until which security
> > support
> > will exist. We might also want to add a third "status" row. e.g.
> > "Supported", "Security Support only", "EOL" (we'll deal with extended
> > support by a third party when that next arises).
> > 
> > I'm happy to make the edits, however I don't know what dates I would
> > write 
> > here. Taking it to be 18 months of Support and a further 18 months of
> > security support I would get:
> > 
> >  			Xen 4.0 	Xen 4.1 	Xen 4.2 	Xen 4.3 	Xen 4.4 	Xen 4.5 	Xen 4.6
> > Initial Release 	7 April 2010 	25 March 2011 	17 Sept 2012 	9 July 2013 	10 March 
> > 2014 	15 Jan 2015 	13 Oct 2015 
> > Supported until		EOL - ???	EOL - ???	EOL - ???	EOL - Jan 2015	EOL - Sept 2015	July 
> > 2016	April 2017
> > Security support til	EOL - ???	EOL - ???	EOL - ???	July 2016	March 2016	Jan 
> > 2017	Oct 2018
> 
> 4.4 is going to have normal support ended with the 4.4.4 release only;
> 4.4.3 got released a little too early from that perspective.

Meaning it will be earlier later than September 2015.

4.4.3 was released in August which was too soon.

I think it is right to err on the side of stopping later than we said.

Did we stop adding backports to staging-4.4 in September, i.e. is 4.4.4
going to be fixes from August-September + security issues until the release
date?

> 
> > (maybe those EOLs - ??? could be whatever the respective dates were, I
> > didn't try and backtrack to try and find out if reality matched the
> > plan)
> 
> At least for the older ones it's probably not worth to reconstruct. 4.2
> had
> its security support ended in Sept 2015.

Thanks.

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

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

  reply	other threads:[~2016-01-07 12:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-06 18:28 [qemu-upstream-4.2-testing test] 77180: regressions - FAIL osstest service owner
2016-01-07  9:56 ` Ian Campbell
2016-01-07 11:22   ` Which trees are supported (Was: Re: [qemu-upstream-4.2-testing test] 77180: regressions - FAIL) Ian Campbell
2016-01-07 11:45     ` Jan Beulich
2016-01-07 12:00       ` Ian Campbell [this message]
2016-01-07 13:12         ` Jan Beulich
2016-01-07 16:02         ` Ian Jackson
2016-01-07 12:44       ` Lars Kurth
2016-01-07 13:09         ` Ian Campbell
2016-01-22  9:22     ` Ian Campbell
2016-01-08 12:10   ` [qemu-upstream-4.2-testing test] 77180: regressions - FAIL Ian Jackson
2016-01-14  9:54     ` Ian Campbell

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=1452168058.21055.203.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=lars.kurth@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /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).