* [Qemu-devel] [RFC] QEMU 2.10 release schedule
@ 2017-05-30 10:11 Stefan Hajnoczi
2017-05-30 11:07 ` Paolo Bonzini
` (2 more replies)
0 siblings, 3 replies; 9+ messages in thread
From: Stefan Hajnoczi @ 2017-05-30 10:11 UTC (permalink / raw)
To: qemu-devel; +Cc: Peter Maydell, Christian Borntraeger
Here is a first stab at the next release schedule:
Beginning of development phase: 2017-04-20
Soft feature freeze: 2017-07-18
-rc0: 2017-07-25
-rc1: 2017-08-01
-rc2: 2017-08-08
-rc3: 2017-08-15
-rc4: 2017-08-22
Thoughts?
Stefan
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-05-30 10:11 [Qemu-devel] [RFC] QEMU 2.10 release schedule Stefan Hajnoczi
@ 2017-05-30 11:07 ` Paolo Bonzini
2017-05-30 11:21 ` Christian Borntraeger
2017-05-31 14:25 ` Peter Maydell
2 siblings, 0 replies; 9+ messages in thread
From: Paolo Bonzini @ 2017-05-30 11:07 UTC (permalink / raw)
To: Stefan Hajnoczi, qemu-devel; +Cc: Peter Maydell, Christian Borntraeger
On 30/05/2017 12:11, Stefan Hajnoczi wrote:
> Here is a first stab at the next release schedule:
>
> Beginning of development phase: 2017-04-20
> Soft feature freeze: 2017-07-18
> -rc0: 2017-07-25
> -rc1: 2017-08-01
> -rc2: 2017-08-08
> -rc3: 2017-08-15
> -rc4: 2017-08-22
>
> Thoughts?
Looks good to me.
Paolo
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-05-30 10:11 [Qemu-devel] [RFC] QEMU 2.10 release schedule Stefan Hajnoczi
2017-05-30 11:07 ` Paolo Bonzini
@ 2017-05-30 11:21 ` Christian Borntraeger
2017-05-31 13:06 ` Stefan Hajnoczi
2017-05-31 14:25 ` Peter Maydell
2 siblings, 1 reply; 9+ messages in thread
From: Christian Borntraeger @ 2017-05-30 11:21 UTC (permalink / raw)
To: Stefan Hajnoczi, qemu-devel; +Cc: Peter Maydell
On 05/30/2017 12:11 PM, Stefan Hajnoczi wrote:
> Here is a first stab at the next release schedule:
>
> Beginning of development phase: 2017-04-20
> Soft feature freeze: 2017-07-18
> -rc0: 2017-07-25
> -rc1: 2017-08-01
> -rc2: 2017-08-08
> -rc3: 2017-08-15
> -rc4: 2017-08-22
>
- rc4/release or really only rc4?
> Thoughts?
> Stefan
>
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-05-30 11:21 ` Christian Borntraeger
@ 2017-05-31 13:06 ` Stefan Hajnoczi
2017-06-07 18:24 ` Marc-André Lureau
0 siblings, 1 reply; 9+ messages in thread
From: Stefan Hajnoczi @ 2017-05-31 13:06 UTC (permalink / raw)
To: Christian Borntraeger; +Cc: qemu-devel, Peter Maydell
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
On Tue, May 30, 2017 at 01:21:01PM +0200, Christian Borntraeger wrote:
> On 05/30/2017 12:11 PM, Stefan Hajnoczi wrote:
> > Here is a first stab at the next release schedule:
> >
> > Beginning of development phase: 2017-04-20
> > Soft feature freeze: 2017-07-18
> > -rc0: 2017-07-25
> > -rc1: 2017-08-01
> > -rc2: 2017-08-08
> > -rc3: 2017-08-15
> > -rc4: 2017-08-22
> >
>
> - rc4/release or really only rc4?
I had rc4/release in mind.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-05-31 13:06 ` Stefan Hajnoczi
@ 2017-06-07 18:24 ` Marc-André Lureau
2017-06-08 10:13 ` Stefan Hajnoczi
0 siblings, 1 reply; 9+ messages in thread
From: Marc-André Lureau @ 2017-06-07 18:24 UTC (permalink / raw)
To: Stefan Hajnoczi, Christian Borntraeger; +Cc: Peter Maydell, qemu-devel
Hi
On Wed, May 31, 2017 at 5:07 PM Stefan Hajnoczi <stefanha@gmail.com> wrote:
> On Tue, May 30, 2017 at 01:21:01PM +0200, Christian Borntraeger wrote:
> > On 05/30/2017 12:11 PM, Stefan Hajnoczi wrote:
> > > Here is a first stab at the next release schedule:
> > >
> > > Beginning of development phase: 2017-04-20
> > > Soft feature freeze: 2017-07-18
> > > -rc0: 2017-07-25
> > > -rc1: 2017-08-01
> > > -rc2: 2017-08-08
> > > -rc3: 2017-08-15
> > > -rc4: 2017-08-22
> > >
> >
> > - rc4/release or really only rc4?
>
> I had rc4/release in mind.
>
Can we put that preliminary schedule on the wiki?
http://wiki.qemu.org/Planning/2.10
Thanks
--
Marc-André Lureau
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-06-07 18:24 ` Marc-André Lureau
@ 2017-06-08 10:13 ` Stefan Hajnoczi
0 siblings, 0 replies; 9+ messages in thread
From: Stefan Hajnoczi @ 2017-06-08 10:13 UTC (permalink / raw)
To: Marc-André Lureau; +Cc: Christian Borntraeger, Peter Maydell, qemu-devel
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
On Wed, Jun 07, 2017 at 06:24:24PM +0000, Marc-André Lureau wrote:
> Hi
>
> On Wed, May 31, 2017 at 5:07 PM Stefan Hajnoczi <stefanha@gmail.com> wrote:
>
> > On Tue, May 30, 2017 at 01:21:01PM +0200, Christian Borntraeger wrote:
> > > On 05/30/2017 12:11 PM, Stefan Hajnoczi wrote:
> > > > Here is a first stab at the next release schedule:
> > > >
> > > > Beginning of development phase: 2017-04-20
> > > > Soft feature freeze: 2017-07-18
> > > > -rc0: 2017-07-25
> > > > -rc1: 2017-08-01
> > > > -rc2: 2017-08-08
> > > > -rc3: 2017-08-15
> > > > -rc4: 2017-08-22
> > > >
> > >
> > > - rc4/release or really only rc4?
> >
> > I had rc4/release in mind.
> >
>
> Can we put that preliminary schedule on the wiki?
> http://wiki.qemu.org/Planning/2.10
Yes, I have posted the schedule on the wiki:
http://wiki.qemu.org/Planning/2.10
No one had concerns about the dates so I think we can consider them
final.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-05-30 10:11 [Qemu-devel] [RFC] QEMU 2.10 release schedule Stefan Hajnoczi
2017-05-30 11:07 ` Paolo Bonzini
2017-05-30 11:21 ` Christian Borntraeger
@ 2017-05-31 14:25 ` Peter Maydell
2017-05-31 15:18 ` Alex Bennée
2 siblings, 1 reply; 9+ messages in thread
From: Peter Maydell @ 2017-05-31 14:25 UTC (permalink / raw)
To: Stefan Hajnoczi; +Cc: qemu-devel, Christian Borntraeger
On 30 May 2017 at 11:11, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> Here is a first stab at the next release schedule:
>
> Beginning of development phase: 2017-04-20
> Soft feature freeze: 2017-07-18
> -rc0: 2017-07-25
> -rc1: 2017-08-01
> -rc2: 2017-08-08
> -rc3: 2017-08-15
> -rc4: 2017-08-22
Are we going with the same definitions of soft/hard freeze
as last time around?
(I thought last release was a complete mess in terms of
getting code in in an orderly manner for the freeze,
personally...)
thanks
-- PMM
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-05-31 14:25 ` Peter Maydell
@ 2017-05-31 15:18 ` Alex Bennée
2017-06-08 10:14 ` Stefan Hajnoczi
0 siblings, 1 reply; 9+ messages in thread
From: Alex Bennée @ 2017-05-31 15:18 UTC (permalink / raw)
To: Peter Maydell; +Cc: Stefan Hajnoczi, Christian Borntraeger, qemu-devel
Peter Maydell <peter.maydell@linaro.org> writes:
> On 30 May 2017 at 11:11, Stefan Hajnoczi <stefanha@gmail.com> wrote:
>> Here is a first stab at the next release schedule:
>>
>> Beginning of development phase: 2017-04-20
>> Soft feature freeze: 2017-07-18
>> -rc0: 2017-07-25
>> -rc1: 2017-08-01
>> -rc2: 2017-08-08
>> -rc3: 2017-08-15
>> -rc4: 2017-08-22
>
> Are we going with the same definitions of soft/hard freeze
> as last time around?
>
> (I thought last release was a complete mess in terms of
> getting code in in an orderly manner for the freeze,
> personally...)
Do we want to have a broad plan for the order things need to go in
before the feature freeze or stick to a first to the gate approach?
Obviously we don't want to stall the process waiting for delayed series
that might end up getting dropped but having the broad sketches might
make it easier for developers to prioritise what patches queues to drain
first?
--
Alex Bennée
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
2017-05-31 15:18 ` Alex Bennée
@ 2017-06-08 10:14 ` Stefan Hajnoczi
0 siblings, 0 replies; 9+ messages in thread
From: Stefan Hajnoczi @ 2017-06-08 10:14 UTC (permalink / raw)
To: Alex Bennée; +Cc: Peter Maydell, Christian Borntraeger, qemu-devel
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
On Wed, May 31, 2017 at 04:18:41PM +0100, Alex Bennée wrote:
>
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > On 30 May 2017 at 11:11, Stefan Hajnoczi <stefanha@gmail.com> wrote:
> >> Here is a first stab at the next release schedule:
> >>
> >> Beginning of development phase: 2017-04-20
> >> Soft feature freeze: 2017-07-18
> >> -rc0: 2017-07-25
> >> -rc1: 2017-08-01
> >> -rc2: 2017-08-08
> >> -rc3: 2017-08-15
> >> -rc4: 2017-08-22
> >
> > Are we going with the same definitions of soft/hard freeze
> > as last time around?
> >
> > (I thought last release was a complete mess in terms of
> > getting code in in an orderly manner for the freeze,
> > personally...)
>
> Do we want to have a broad plan for the order things need to go in
> before the feature freeze or stick to a first to the gate approach?
>
> Obviously we don't want to stall the process waiting for delayed series
> that might end up getting dropped but having the broad sketches might
> make it easier for developers to prioritise what patches queues to drain
> first?
Any further thoughts on this? Otherwise we can default to the way
things were done in previous releases.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2017-06-08 10:14 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-05-30 10:11 [Qemu-devel] [RFC] QEMU 2.10 release schedule Stefan Hajnoczi
2017-05-30 11:07 ` Paolo Bonzini
2017-05-30 11:21 ` Christian Borntraeger
2017-05-31 13:06 ` Stefan Hajnoczi
2017-06-07 18:24 ` Marc-André Lureau
2017-06-08 10:13 ` Stefan Hajnoczi
2017-05-31 14:25 ` Peter Maydell
2017-05-31 15:18 ` Alex Bennée
2017-06-08 10:14 ` Stefan Hajnoczi
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).