From: George Dunlap <george.dunlap@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Lars Kurth <lars.kurth.xen@gmail.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>,
DougGoldstein <cardoe@cardoe.com>,
committers@xenproject.org
Subject: Re: Next 4.6.x stable release, numbering, qemu-tag
Date: Wed, 15 Jun 2016 10:35:03 +0100 [thread overview]
Message-ID: <57612147.5070101@citrix.com> (raw)
In-Reply-To: <5761222102000078000F51B6@prv-mh.provo.novell.com>
On 15/06/16 08:38, Jan Beulich wrote:
> As said on IRC this morning, while I continue to by unconvinced of the
> arguments, being the only one wanting to stick with 4.6.2 I'm not going
> to argue any further on this - be it 4.6.3 then. The only thing I would
> really like to ask is that this time (as should have happened in the first
> place), before tagging respective trees, everyone please make sure
> everything intended to be in the tree they're responsible for indeed is
> there. I really want to be able to rely on everybody having their trees
> (or parts thereof) under control.
I think this is an unreasonable expectation -- how is someone supposed
to know whether a new critical issue is going to be reported seconds
after they sign and push the tag? It amounts to saying, "Please make
sure there are no bugs in your tree."
The version of qemu-xen that was tagged with 4.6 had been through
several rounds of RCs, months of osstesting, and even through a slew of
builds on Travis (which does build Ubuntu, but apparently just not the
bleeding-edge version). I only happened to notice it as I was trying to
get patches for raisin for 4.7.
I am going to try to get build tests for a wide range of distros on a
regular basis, which will close this particular kind of bug. But there
are innumerable other types of bug which still won't be caught; that's
just a fact of software development.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-15 9:36 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
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 [this message]
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=57612147.5070101@citrix.com \
--to=george.dunlap@citrix.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).