[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] release retrospective, next release timing, numbering
From: |
David Gibson |
Subject: |
Re: [Qemu-devel] release retrospective, next release timing, numbering |
Date: |
Thu, 3 May 2018 11:04:30 +1000 |
User-agent: |
Mutt/1.9.3 (2018-01-21) |
On Mon, Apr 30, 2018 at 04:23:59PM +0200, Greg Kurz wrote:
> On Fri, 27 Apr 2018 16:51:03 +0100
> Peter Maydell <address@hidden> wrote:
>
> > Hi; I usually let people forget about releases for a month or
> > so before bringing this topic up, but:
> >
> > (1) do we want to call the next release 2.13, or something else?
> > There's no particular reason to bump to 3.0 except some combination of
> > * if we keep going like this we'll get up to 2.42, which starts to
> > get silly
> > * Linus-style "avoid being too predictable"
> > * triskaidekaphobia
> > but maybe we should anyway?
> >
>
> Do we care for machine versions to stick to QEMU versions ? I ask,
> because we've already added a pseries-2.13 machine type (in master
> since David's latest pull req). No big deal though if we have to
> turn it into pseries-3.0 I guess...
We definitely want this to match the overall release name, so we'll
need to change it if we decide on something other than 2.13.
>
> > (2) release timing:
> > * usual schedule would give us a next release mid-to-late August
> > * unless I can persuade Stefan to do the release management this
> > cycle we might need to wind that in by a couple of weeks so
> > it's definitely done by the middle of August, to avoid a clash
> > with a personal commitment
> > * so probably hardfreeze 10th July, softfreeze 3rd July
> >
> > (3) retrospective, lessons learned &c
> > * please remember that if every single submaintainer submits
> > a pull request on the morning of an RC, it is physically
> > not possible for me to process all those pulls in time to
> > tag the RC that day. We had several RCs which got delayed
> > by a day because of this; please try to submit earlier
> > rather than later...
> > * provide your opinions here ?
> >
> > thanks
> > -- PMM
> >
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
signature.asc
Description: PGP signature
- Re: [Qemu-devel] release retrospective, next release timing, numbering, (continued)
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Thomas Huth, 2018/05/03
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Daniel P . Berrangé, 2018/05/03
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Cédric Le Goater, 2018/05/03
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Cédric Le Goater, 2018/05/03
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Stefan Hajnoczi, 2018/05/03
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Dr. David Alan Gilbert, 2018/05/03
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Stefan Hajnoczi, 2018/05/04
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Markus Armbruster, 2018/05/04
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Stefan Hajnoczi, 2018/05/04
- Re: [Qemu-devel] release retrospective, next release timing, numbering, Peter Maydell, 2018/05/04
Re: [Qemu-devel] release retrospective, next release timing, numbering,
David Gibson <=
Re: [Qemu-devel] release retrospective, next release timing, numbering, Michal Suchánek, 2018/05/07
Re: [Qemu-devel] release retrospective, next release timing, numbering, Peter Maydell, 2018/05/22
Re: [Qemu-devel] release retrospective, next release timing, numbering, Philippe Mathieu-Daudé, 2018/05/28