xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	Lars Kurth <lars.kurth.xen@gmail.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	committers@xenproject.org, Jan Beulich <JBeulich@suse.com>,
	Anthony PERARD <anthony.perard@citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: Next 4.6.x stable release, numbering, qemu-tag
Date: Tue, 14 Jun 2016 15:27:34 -0400	[thread overview]
Message-ID: <20160614192734.GF28047@char.us.oracle.com> (raw)
In-Reply-To: <22368.17783.295533.273010@mariner.uk.xensource.com>

> And, we ought not to let this issue delay the actual point release and
> it is close to being on the critical path.  A decision is needed.

My personal preferred color is 4.6.2.1 (and I believe we did a similar
release in the past: RELEASE-4.1.6.1)

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

  reply	other threads:[~2016-06-14 19:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <57504E0802000078000F1164@prv-mh.provo.novell.com>
     [not found] ` <20160602140958.GX5160@citrix.com>
     [not found]   ` <575A868402000078000F3D98@prv-mh.provo.novell.com>
     [not found]     ` <22362.38888.298368.190872@mariner.uk.xensource.com>
     [not found]       ` <22362.40282.345007.208511@mariner.uk.xensource.com>
     [not found]         ` <20160610110551.GA1807@perard>
     [not found]           ` <22362.40839.475210.399639@mariner.uk.xensource.com>
     [not found]             ` <575ACFC902000078000F3F49@prv-mh.provo.novell.com>
     [not found]               ` <22362.47886.957478.714311@mariner.uk.xensource.com>
     [not found]                 ` <575AEA4802000078000F3FC8@prv-mh.provo.novell.com>
     [not found]                   ` <22362.58894.967258.687430@mariner.uk.xensource.com>
2016-06-14 17:57                     ` Next 4.6.x stable release, numbering, qemu-tag Ian Jackson
2016-06-14 19:27                       ` Konrad Rzeszutek Wilk [this message]
2016-06-15  8:57                         ` George Dunlap
2016-06-15  9:51                           ` Jan Beulich
2016-06-15  7:38                       ` Jan Beulich
2016-06-15  9:03                         ` Wei Liu
2016-06-15  9:56                           ` Jan Beulich
2016-06-15 10:21                             ` Wei Liu
2016-06-15  9:35                         ` George Dunlap
2016-06-15 10:04                           ` Jan Beulich
2016-06-15 10:13                             ` George Dunlap
2016-06-15 10:25                               ` Jan Beulich
2016-06-15 10:30                                 ` George Dunlap
2016-06-15 10:46                                   ` Jan Beulich
2016-06-15 11:46                                     ` George Dunlap

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=20160614192734.GF28047@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=JBeulich@suse.com \
    --cc=anthony.perard@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=committers@xenproject.org \
    --cc=ian.jackson@eu.citrix.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.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 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).