From: "Justin M. Forbes" <jmforbes@linuxtx.org>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-stable@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Qemu-stable] Last call for 1.0.1 stable release
Date: Tue, 10 Jan 2012 17:30:33 -0600 [thread overview]
Message-ID: <1326238235.28119.7.camel@paddy.linuxtx.org> (raw)
In-Reply-To: <4F0C3E11.2070309@suse.de>
On Tue, 2012-01-10 at 14:33 +0100, Andreas Färber wrote:
> Justin,
>
> Am 09.01.2012 19:00, schrieb Justin M. Forbes:
> > Due to the repository move, holidays and other bits, we are a bit late
> > getting out the door, but I want to get qemu 1.0.1 stable release done this
> > week. We have a number of patches, but if you are sitting on anything or
> > close to finishing up something, please get all patches to
> > qemu-stable@nongnu.org by Wednesday Jan 11th to give time for testing
> > before the release is cut.
>
> Could you be a bit more verbose, please? Currently, judging by
> http://git.qemu.org/?p=qemu-stable-1.0.git;a=summary (which seems to be
> lacking a v1.0 tag), it seems like only a Malta fix is queued so far?
>
> I'm new to the stable business but my expectation is that patches are
> cherry-picked to the stable branch, if qualified, once applied to
> master. I haven't seen any "Thanks, applied to stable-1.0 branch" reply
> lately, but you're pinning 1.0.1 to a date already, leading to 1.0.1
> getting either no testing (if you apply pending patches today/tomorrow)
> or hardly any fixes (one applied 47 hours ago)...
>
The tree is currently updated with everything from my queue, and I have
already started some testing with what we have. The expectation of
patches by Wednesday means that no patches received after that day will
be applied for 1.0.1 unless they are to fix a problem in what I have
received. Anything else will be applied toward 1.0.2. Essentially we
have to make a release, and there is a good bit of testing required for
a release, so the tree has to freeze at some point for that to happen.
Justin
next prev parent reply other threads:[~2012-01-10 23:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 18:00 [Qemu-devel] Last call for 1.0.1 stable release Justin M. Forbes
2012-01-10 13:33 ` [Qemu-devel] [Qemu-stable] " Andreas Färber
2012-01-10 23:30 ` Justin M. Forbes [this message]
2012-01-10 16:01 ` [Qemu-devel] " Kevin Wolf
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=1326238235.28119.7.camel@paddy.linuxtx.org \
--to=jmforbes@linuxtx.org \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.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).