[Qemu-devel] We have now entered 1.0 hard freeze

[Qemu-devel] We have now entered 1.0 hard freeze

[Anthony Liguori]

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

[1] http://wiki.qemu.org/ChangeLog/Next

[2] http://wiki.qemu.org/Planning/1.0/Testing

Regards,

Anthony Liguori

Re: [Qemu-devel] We have now entered 1.0 hard freeze

[Alon Levy]

[-- 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

Re: [Qemu-devel] We have now entered 1.0 hard freeze

[Max Filippov]

Hi.

> 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.

My pull request for the xtensa
(http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg03962.html)
haven't got any attention.
I can resend it, should you reconsider applying it, or I can resend
only 'fixes'-part of it.

And also I'd like it to be clarified, whether I should consider myself
a contributor or a submaintainer.

> 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.

-- 
Thanks.
-- Max

Re: [Qemu-devel] We have now entered 1.0 hard freeze

[Anthony Liguori]

On 11/02/2011 08:08 AM, Max Filippov wrote:
> Hi.
>
>> 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.
>
> My pull request for the xtensa
> (http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg03962.html)
> haven't got any attention.

I'm expecting Blue to pull that.  It made it in time for 1.0.  The same is true 
for TCGi.

> I can resend it, should you reconsider applying it, or I can resend
> only 'fixes'-part of it.
>
> And also I'd like it to be clarified, whether I should consider myself
> a contributor or a submaintainer.

If you do PULL requests, you're a submaintainer :-)

Regards,

Anthony Liguori

>> 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.
>

Re: [Qemu-devel] We have now entered 1.0 hard freeze

[Peter Maydell]

On 2 November 2011 13:10, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 11/02/2011 08:08 AM, Max Filippov wrote:
>> And also I'd like it to be clarified, whether I should consider myself
>> a contributor or a submaintainer.
>
> If you do PULL requests, you're a submaintainer :-)

Speaking as somebody who spent a while in a not dissimilar position
to Max, I think the key question is not whether you make a pullreq
but whether you have any confidence it's going to be applied...

  "I can call spirits from the vasty deep."
  "Why, so can I, or so can any man;
   But will they come when you do call for them?"

-- PMM

Re: [Qemu-devel] We have now entered 1.0 hard freeze

[Blue Swirl]

On Wed, Nov 2, 2011 at 13:10, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 11/02/2011 08:08 AM, Max Filippov wrote:
>>
>> Hi.
>>
>>> 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.
>>
>> My pull request for the xtensa
>> (http://lists.nongnu.org/archive/html/qemu-devel/2011-10/msg03962.html)
>> haven't got any attention.
>
> I'm expecting Blue to pull that.  It made it in time for 1.0.  The same is
> true for TCGi.

OK, I'll pull.

>> I can resend it, should you reconsider applying it, or I can resend
>> only 'fixes'-part of it.
>>
>> And also I'd like it to be clarified, whether I should consider myself
>> a contributor or a submaintainer.
>
> If you do PULL requests, you're a submaintainer :-)
>
> Regards,
>
> Anthony Liguori
>
>>> 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.
>>
>
>

Re: [Qemu-devel] We have now entered 1.0 hard freeze

[Rick Vernam]

On Tuesday 01 November 2011 19:43:53 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
> 
> [1] http://wiki.qemu.org/ChangeLog/Next
> 
> [2] http://wiki.qemu.org/Planning/1.0/Testing
> 
> Regards,
> 
> Anthony Liguori

I would like to test Spice & Virt-IO against Windows XP guests.
If anybody contributes testing plans for Spice and/or Virt-IO, I would 
encourage them to include information about what versions of the other 
software to use in testing, including the windows drivers.  It would also be 
useful to know how to obtain other required software.  For example, it would 
be hard to test the qemu side of spice and virt-io if the guest drivers and 
services were not also available.

Thanks,
-Rick