From: Anthony Liguori <aliguori@us.ibm.com>
To: "Johnson, Eric" <ericj@mips.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [RFC] 1.4 release schedule
Date: Mon, 03 Dec 2012 15:41:35 -0600 [thread overview]
Message-ID: <878v9en78w.fsf@codemonkey.ws> (raw)
In-Reply-To: <AD431C1EF67D4B4B801AEC089EB7ED4801448953CC@exchdb03.mips.com>
"Johnson, Eric" <ericj@mips.com> writes:
> I think you meant to change the 1.3.0 to 1.4.0 for the milestones on
> the Wiki. ;-)
Indeed, fixed now.
Regards,
Anthony Liguori
>
>> -----Original Message-----
>> From: qemu-devel-bounces+ericj=mips.com@nongnu.org [mailto:qemu-devel-
>> bounces+ericj=mips.com@nongnu.org] On Behalf Of Anthony Liguori
>> Sent: Monday, December 03, 2012 1:30 PM
>> To: qemu-devel@nongnu.org
>> Subject: [Qemu-devel] [RFC] 1.4 release schedule
>>
>>
>> Hi,
>>
>> Based on popular demand, I'd like to continue with a 3-month release
>> cycle for the foreseeable future. One thing I'd like to "fix" though is
>> to avoid major holidays during the -rc cycles.
>>
>> The best cycle I can figure is:
>>
>> Feb 15th
>> May 15th
>> Aug 15th
>> Nov 15th
>>
>> To get us onto this schedule, we'll need to make 1.4 a short release but
>> I still think there's ample time to ge stuff done.
>>
>> I've put up a strawman schedule on the wiki:
>>
>> http://wiki.qemu.org/Planning/1.4
>>
>> Regards,
>>
>> Anthony Liguori
>>
next prev parent reply other threads:[~2012-12-03 21:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 21:30 [Qemu-devel] [RFC] 1.4 release schedule Anthony Liguori
2012-12-03 21:34 ` Johnson, Eric
2012-12-03 21:41 ` Anthony Liguori [this message]
2012-12-04 18:38 ` Blue Swirl
2012-12-04 18:42 ` Peter Maydell
2012-12-04 19:16 ` Blue Swirl
2012-12-04 22:00 ` Anthony Liguori
2012-12-05 19:28 ` Blue Swirl
2012-12-05 19:41 ` Hans de Goede
2012-12-05 19:58 ` Blue Swirl
2012-12-06 8:05 ` Markus Armbruster
2012-12-06 21:27 ` Blue Swirl
2012-12-06 10:19 ` Kevin Wolf
2012-12-06 21:45 ` Blue Swirl
2012-12-06 9:01 ` Andreas Färber
2012-12-06 21:35 ` Blue Swirl
2012-12-04 18:41 ` Peter Maydell
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=878v9en78w.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=ericj@mips.com \
--cc=qemu-devel@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).