xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org, committers@xenproject.org,
	Wei Liu <wei.liu2@citrix.com>
Subject: Re: Commit moratorium for branching 4.7
Date: Tue, 7 Jun 2016 17:00:38 +0100	[thread overview]
Message-ID: <20160607160038.GH5714@citrix.com> (raw)
In-Reply-To: <22358.53851.305858.396704@mariner.uk.xensource.com>

On Tue, Jun 07, 2016 at 02:55:39PM +0100, Ian Jackson wrote:
> Ian Jackson writes ("Commit moratorium for branching 4.7"):
> > At Wei's request, I am starting to branch the tree, so that
> > xen-unstable can diverge from the *-4.7 preparation branches.
> > 
> > Please don't commit anything until I'm done, which will be later
> > today.
> I have now finished this branching process.  Please let me know of any
> anomalies.  I have applied the patch below to xen.git#staging, to
> (from a technical point of view) open Xen 4.8.
> I'm not sure we have made a community decision about the terms under
> which patches may be committed to the newly-open 4.8 (and who is
> responsible for porting bug fixes from 4.7 to 4.8 or vice versa).
> Perhaps I missed the email.  I don't think the stable tree maintainers
> want to take over 4.7 yet.  So until that is settled, probably nothing
> substantial should be committed to 4.8.

I forgot to send an email about this, sorry.

From the point on up to the actual release, all committers are
responsible for both 4.7 and -unstable branch. Bug fixes can be first
committed -unstable (no RM ack needed) and then cherry-pick (with RM
ack) to 4.7 branch.

I don't expect there to be large number of patches though.


Xen-devel mailing list

      parent reply	other threads:[~2016-06-07 16:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <22358.51377.974810.863351@mariner.uk.xensource.com>
2016-06-07 13:55 ` Commit moratorium for branching 4.7 Ian Jackson
2016-06-07 14:26   ` Jan Beulich
2016-06-07 14:41     ` George Dunlap
2016-06-07 15:55       ` Ian Jackson
2016-06-07 16:00   ` Wei Liu [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160607160038.GH5714@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=committers@xenproject.org \
    --cc=xen-devel@lists.xenproject.org \


* 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).