All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: xen-devel@lists.xensource.com, Wei Liu <wei.liu2@citrix.com>,
	Lars Kurth <lars.kurth@xen.org>, Jan Beulich <JBeulich@suse.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: Which trees are supported (Was: Re: [qemu-upstream-4.2-testing test] 77180: regressions - FAIL)
Date: Thu, 7 Jan 2016 16:02:01 +0000	[thread overview]
Message-ID: <22158.35833.90014.57330@mariner.uk.xensource.com> (raw)
In-Reply-To: <1452168058.21055.203.camel@citrix.com>

Ian Campbell writes ("Re: [Xen-devel] Which trees are supported (Was: Re: [qemu-upstream-4.2-testing test] 77180: regressions - FAIL)"):
> 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?

My usual approach with backports is to apply them back until either
(a) they don't apply or
(b) I reach the first tree which is out of security support.

In the case (a) I make a personal decision whether to either (i) spend
my own effort adapting the backport or (ii) tell someone (the
submitter, often) and give them the opportunity to supply a backport.

In both cases (a) and (b), the nominal support status of the old tree
is a factor, but not determinative.

I avoid making /any/ changes to trees which are out of security
support, to avoid giving them the appearance of being alive.

Ian.

  parent reply	other threads:[~2016-01-07 16:02 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 [this message]
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=22158.35833.90014.57330@mariner.uk.xensource.com \
    --to=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 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.