[Qemu-devel] QEMU 3.0 proposed release schedule

[Qemu-devel] QEMU 3.0 proposed release schedule

[Peter Maydell]

I've put up a draft release schedule at:
https://wiki.qemu.org/Planning/3.0

2018-04-24      Beginning of development phase
2018-07-03      Soft feature freeze.
2018-07-10      Hard feature freeze. Tag rc0
2018-07-17      Tag rc1
2018-07-24      Tag rc2
2018-07-31      Tag rc3
2018-08-07      Release, or if necessary, tag rc4
2018-08-14      Release, if we needed rc4

It's a touch earlier than last year, so we're definitely
finished before the end of August.

Does this work for people?

thanks
-- PMM

Re: [Qemu-devel] QEMU 3.0 proposed release schedule

[Warner Losh]

On Tue, May 22, 2018 at 9:24 AM, Peter Maydell <peter.maydell@linaro.org>
wrote:

> I've put up a draft release schedule at:
> https://wiki.qemu.org/Planning/3.0
>
> 2018-04-24      Beginning of development phase
> 2018-07-03      Soft feature freeze.
> 2018-07-10      Hard feature freeze. Tag rc0
> 2018-07-17      Tag rc1
> 2018-07-24      Tag rc2
> 2018-07-31      Tag rc3
> 2018-08-07      Release, or if necessary, tag rc4
> 2018-08-14      Release, if we needed rc4
>
> It's a touch earlier than last year, so we're definitely
> finished before the end of August.
>
> Does this work for people?
>

I'd love to get bsd-user into 3.0. At the moment, all the changes are in
bsd-user, and my cleanup is trending to about 50 patches. Given traditional
timelines, when should I submit patches to the mailing list for that?
Alternatively, when would a future 3.1 be expected?

Warner

Re: [Qemu-devel] QEMU 3.0 proposed release schedule

[Peter Maydell]

On 22 May 2018 at 16:39, Warner Losh <imp@bsdimp.com> wrote:
> On Tue, May 22, 2018 at 9:24 AM, Peter Maydell <peter.maydell@linaro.org>
> wrote:
>>
>> I've put up a draft release schedule at:
>> https://wiki.qemu.org/Planning/3.0
>>
>> 2018-04-24      Beginning of development phase
>> 2018-07-03      Soft feature freeze.
>> 2018-07-10      Hard feature freeze. Tag rc0
>> 2018-07-17      Tag rc1
>> 2018-07-24      Tag rc2
>> 2018-07-31      Tag rc3
>> 2018-08-07      Release, or if necessary, tag rc4
>> 2018-08-14      Release, if we needed rc4

> I'd love to get bsd-user into 3.0. At the moment, all the changes are in
> bsd-user, and my cleanup is trending to about 50 patches. Given traditional
> timelines, when should I submit patches to the mailing list for that?

The usual recommendation is to submit early and often.
"softfreeze" means "any new feature to go in must already
be in a pull request on the list by this date", but big
features hitting the list late in the cycle are not fun to
deal with and best avoided. Also, don't feel you need to hold
on to the thing until all 50-odd patches are ready to submit;
if you can break it up into smaller patchsets that's easier
to deal with.

> Alternatively, when would a future 3.1 be expected?

We do 3 releases a year, generally in approximately April, August
and December. So 3.1 will be early December.

thanks
-- PMM

Re: [Qemu-devel] QEMU 3.0 proposed release schedule

[Warner Losh]

On Tue, May 22, 2018 at 9:50 AM, Peter Maydell <peter.maydell@linaro.org>
wrote:

> On 22 May 2018 at 16:39, Warner Losh <imp@bsdimp.com> wrote:
> > On Tue, May 22, 2018 at 9:24 AM, Peter Maydell <peter.maydell@linaro.org
> >
> > wrote:
> >>
> >> I've put up a draft release schedule at:
> >> https://wiki.qemu.org/Planning/3.0
> >>
> >> 2018-04-24      Beginning of development phase
> >> 2018-07-03      Soft feature freeze.
> >> 2018-07-10      Hard feature freeze. Tag rc0
> >> 2018-07-17      Tag rc1
> >> 2018-07-24      Tag rc2
> >> 2018-07-31      Tag rc3
> >> 2018-08-07      Release, or if necessary, tag rc4
> >> 2018-08-14      Release, if we needed rc4
>
> > I'd love to get bsd-user into 3.0. At the moment, all the changes are in
> > bsd-user, and my cleanup is trending to about 50 patches. Given
> traditional
> > timelines, when should I submit patches to the mailing list for that?
>
> The usual recommendation is to submit early and often.
>

Should I do a RFC or preview submission then of the first dozen patches
maybe as I work out integrating back the bug/compile fixes into the early
series? I'd love to get feedback, but don't want to waste people's time on
something that I've not compile tested every change on (just the final
results, which stands today at ~125 changes, but last week was at 200).

Warner

Re: [Qemu-devel] QEMU 3.0 proposed release schedule

[Peter Maydell]

On 22 May 2018 at 17:34, Warner Losh <imp@bsdimp.com> wrote:
> On Tue, May 22, 2018 at 9:50 AM, Peter Maydell <peter.maydell@linaro.org>
> wrote:
>> The usual recommendation is to submit early and often.
>
>
> Should I do a RFC or preview submission then of the first dozen patches
> maybe as I work out integrating back the bug/compile fixes into the early
> series? I'd love to get feedback, but don't want to waste people's time on
> something that I've not compile tested every change on (just the final
> results, which stands today at ~125 changes, but last week was at 200).

I would suggest a preview submission, yes, though if it did
at least compile that would be nice...

-- PMM

Re: [Qemu-devel] QEMU 3.0 proposed release schedule

[Stefan Hajnoczi]

[-- Attachment #1: Type: text/plain, Size: 635 bytes --]

On Tue, May 22, 2018 at 04:24:37PM +0100, Peter Maydell wrote:
> I've put up a draft release schedule at:
> https://wiki.qemu.org/Planning/3.0
> 
> 2018-04-24      Beginning of development phase
> 2018-07-03      Soft feature freeze.
> 2018-07-10      Hard feature freeze. Tag rc0
> 2018-07-17      Tag rc1
> 2018-07-24      Tag rc2
> 2018-07-31      Tag rc3
> 2018-08-07      Release, or if necessary, tag rc4
> 2018-08-14      Release, if we needed rc4
> 
> It's a touch earlier than last year, so we're definitely
> finished before the end of August.
> 
> Does this work for people?

Sounds good to me.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]