From: Alon Levy <alevy@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] We have now entered 1.0 hard freeze
Date: Wed, 2 Nov 2011 10:10:43 +0200 [thread overview]
Message-ID: <20111102080935.GE12373@garlic> (raw)
In-Reply-To: <4EB09249.3050700@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
On Tue, Nov 01, 2011 at 07:43:53PM -0500, Anthony Liguori wrote:
> Hi,
>
> I've just pushed the VERSION update so we are officially in hard freeze.
>
> I've cleared out my patch and pull request queues and processed
> everything I intend on processing for 1.0.
>
> If you're a contributor and have a question about a patch that
> didn't make the hard freeze, please feel free to ask about it, but
> at this point, it's very unlikely to make it to 1.0.
>
> If you're a submaintainer, it's up to you about whether you continue
> taking new features into your tree during the freeze. I would
> strongly encourage it. But only send pull requests that contain bug
> fixes from this point on.
>
> If you've got commit access, please exercise extreme care in what
> you commit to the tree at this stage. We should be in a bug-fix
> phase only now.
>
> The remaining release schedule is included below. I'd like to take
> a moment to encourage everyone to update the 1.0 ChangeLog[1] and
> contribute to the testing plan[2]. Happy testing!
>
> | 2011-11-07
> | Tag qemu-1.0-rc1. [[Planning/1.0/Testing|Test Day]]
> |-
> | 2011-11-14
> | Tag qemu-1.0-rc2
> |-
> | 2011-11-21
> | Tag qemu-1.0-rc3
> |-
> | 2011-11-28
> | Tag qemu-1.0-rc4
> |-
> | 2011-12-01
> | Tag qemu-1.0
Attaching an ical file I used to import this to evolution in case it may
help anyone.
>
> [1] http://wiki.qemu.org/ChangeLog/Next
>
> [2] http://wiki.qemu.org/Planning/1.0/Testing
>
> Regards,
>
> Anthony Liguori
>
>
[-- Attachment #2: qemu-1.0.ical --]
[-- Type: text/plain, Size: 762 bytes --]
BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//PYVOBJECT//NONSGML Version 1//EN
BEGIN:VEVENT
UID:20111102T080327Z-54281@garlic
DTSTART:20111107T000000
DTEND:20111107T010000
SUMMARY:Tag qemu-1.0-rc1. [[Planning/1.0/Testing|Test Day]]
END:VEVENT
BEGIN:VEVENT
UID:20111102T080327Z-57726@garlic
DTSTART:20111114T000000
DTEND:20111114T010000
SUMMARY:Tag qemu-1.0-rc2
END:VEVENT
BEGIN:VEVENT
UID:20111102T080327Z-70196@garlic
DTSTART:20111121T000000
DTEND:20111121T010000
SUMMARY:Tag qemu-1.0-rc3
END:VEVENT
BEGIN:VEVENT
UID:20111102T080327Z-41860@garlic
DTSTART:20111128T000000
DTEND:20111128T010000
SUMMARY:Tag qemu-1.0-rc4
END:VEVENT
BEGIN:VEVENT
UID:20111102T080327Z-41366@garlic
DTSTART:20111201T000000
DTEND:20111201T010000
SUMMARY:Tag qemu-1.0
END:VEVENT
END:VCALENDAR
next prev parent reply other threads:[~2011-11-02 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-02 0:43 [Qemu-devel] We have now entered 1.0 hard freeze Anthony Liguori
2011-11-02 8:10 ` Alon Levy [this message]
2011-11-02 13:08 ` Max Filippov
2011-11-02 13:10 ` Anthony Liguori
2011-11-02 13:21 ` Peter Maydell
2011-11-02 20:00 ` Blue Swirl
2011-11-02 22:14 ` Rick Vernam
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=20111102080935.GE12373@garlic \
--to=alevy@redhat.com \
--cc=aliguori@us.ibm.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).