xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth.xen@gmail.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel@lists.xensource.com, WeiLiu <wei.liu2@citrix.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.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:44:28 +0000	[thread overview]
Message-ID: <5E76374B-EEBA-4C0B-A157-85E4F57DBEE3@gmail.com> (raw)
In-Reply-To: <568E5DF902000078000C4542@prv-mh.provo.novell.com>


> On 7 Jan 2016, at 11:45, Jan Beulich <JBeulich@suse.com> 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:

Ian, that would be great. Can you ping me when done?
I still have an open action to come up with an approach to include information in this table in in-tree documentation
Lars

  parent reply	other threads:[~2016-01-07 12:44 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
2016-01-07 13:12         ` Jan Beulich
2016-01-07 16:02         ` Ian Jackson
2016-01-07 12:44       ` Lars Kurth [this message]
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=5E76374B-EEBA-4C0B-A157-85E4F57DBEE3@gmail.com \
    --to=lars.kurth.xen@gmail.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=ian.campbell@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).