* [Qemu-devel] Last call for 1.0.1 stable release @ 2012-01-09 18:00 Justin M. Forbes 2012-01-10 13:33 ` [Qemu-devel] [Qemu-stable] " Andreas Färber 2012-01-10 16:01 ` [Qemu-devel] " Kevin Wolf 0 siblings, 2 replies; 4+ messages in thread From: Justin M. Forbes @ 2012-01-09 18:00 UTC (permalink / raw) To: qemu-stable; +Cc: qemu-devel 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. Thanks, Justin ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [Qemu-stable] Last call for 1.0.1 stable release 2012-01-09 18:00 [Qemu-devel] Last call for 1.0.1 stable release Justin M. Forbes @ 2012-01-10 13:33 ` Andreas Färber 2012-01-10 23:30 ` Justin M. Forbes 2012-01-10 16:01 ` [Qemu-devel] " Kevin Wolf 1 sibling, 1 reply; 4+ messages in thread From: Andreas Färber @ 2012-01-10 13:33 UTC (permalink / raw) To: Justin M. Forbes; +Cc: qemu-stable, qemu-devel 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)... Regards, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] [Qemu-stable] Last call for 1.0.1 stable release 2012-01-10 13:33 ` [Qemu-devel] [Qemu-stable] " Andreas Färber @ 2012-01-10 23:30 ` Justin M. Forbes 0 siblings, 0 replies; 4+ messages in thread From: Justin M. Forbes @ 2012-01-10 23:30 UTC (permalink / raw) To: Andreas Färber; +Cc: qemu-stable, qemu-devel 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 ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [Qemu-devel] Last call for 1.0.1 stable release 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 16:01 ` Kevin Wolf 1 sibling, 0 replies; 4+ messages in thread From: Kevin Wolf @ 2012-01-10 16:01 UTC (permalink / raw) To: Justin M. Forbes; +Cc: qemu-stable, qemu-devel 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. I would suggest cherry-picking the following commits that went through my tree: b9c5329 rbd: always set out parameter in qemu_rbd_snap_list 3763f26 Documentation: Add qemu-img -t parameter in man page 87a1b3e qemu-img rebase: Fix for undersized backing files 39a7a36 coroutine: switch per-thread free pool to a global pool bd83b36 qiov: prevent double free or use-after-free Kevin ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2012-01-10 23:30 UTC | newest] Thread overview: 4+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 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 2012-01-10 16:01 ` [Qemu-devel] " Kevin Wolf
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).