From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, Thomas Huth <thuth@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] release retrospective, next release timing, numbering
Date: Thu, 3 May 2018 10:07:27 +0100 [thread overview]
Message-ID: <20180503090727.GC11382@redhat.com> (raw)
In-Reply-To: <20180503072100.GA5301@stefanha-x1.localdomain>
On Thu, May 03, 2018 at 08:21:00AM +0100, Stefan Hajnoczi wrote:
> On Wed, May 02, 2018 at 09:02:00AM +0100, Daniel P. Berrangé wrote:
> > On Wed, May 02, 2018 at 09:44:03AM +0200, Gerd Hoffmann wrote:
> > > Hi,
> > >
> > > > > If we bump the major version each year anyway, why not go the whole way
> > > > > and use 2018.1, 2018.2, ... (or even <year>.<month>)? The nice thing
> > > > > about that is that you can see at a glance when the release took place.
> > > >
> > > > ... or simply drop the first two digits and call them 18.1, 18.2, ...?
> >
> > > We could also drop the major/minor scheme altogether (as they are
> > > meaningless anyway) and just go for YYMM, i.e. 1808 (for a august
> > > release).
> >
> > I don't much like that - it'll lead to a wierd progression of numbers
> > where we'll be constantly the rationale re-explaining to people who
> > want to know why we've jumped from 1808 to 1902 to 1905 etc
>
> I don't see an issue with time-based numbering schemes. Ubuntu made it
> popular and other projects (like DPDK) are doing the same thing now.
>
> The convention is YY.MM though, not YYMM.
It feels like we've got quite a strong backing for time based versioning
amongst people replying here. I'd be happy with YY.MM
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2018-05-03 9:07 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 15:51 [Qemu-devel] release retrospective, next release timing, numbering Peter Maydell
2018-04-27 16:17 ` Thomas Huth
2018-04-27 16:24 ` Peter Maydell
2018-04-27 16:42 ` Thomas Huth
2018-04-30 10:06 ` Paolo Bonzini
2018-04-30 10:11 ` Peter Maydell
2018-05-02 11:58 ` Daniel P. Berrangé
2018-05-02 12:05 ` Peter Maydell
2018-05-03 9:33 ` Daniel P. Berrangé
2018-05-03 9:42 ` Thomas Huth
2018-05-03 9:45 ` Daniel P. Berrangé
2018-05-03 14:01 ` Cédric Le Goater
2018-05-03 14:16 ` Cédric Le Goater
2018-05-03 18:02 ` Stefan Hajnoczi
2018-05-03 18:50 ` Dr. David Alan Gilbert
2018-05-04 8:29 ` Stefan Hajnoczi
2018-05-04 5:29 ` Markus Armbruster
2018-05-04 8:16 ` Stefan Hajnoczi
2018-05-04 8:24 ` Peter Maydell
2018-04-27 19:01 ` Michal Suchánek
2018-04-29 14:56 ` Richard Henderson
2018-05-02 10:41 ` Laszlo Ersek
2018-05-02 11:51 ` Peter Maydell
2018-05-07 18:12 ` Michal Suchánek
2018-04-30 10:35 ` Daniel P. Berrangé
2018-05-02 7:29 ` Markus Armbruster
2018-05-02 8:16 ` Daniel P. Berrangé
2018-05-02 9:44 ` Cornelia Huck
2018-04-30 9:29 ` Cornelia Huck
2018-04-30 10:01 ` Peter Maydell
2018-04-30 10:33 ` Daniel P. Berrangé
2018-04-30 11:21 ` Cornelia Huck
2018-04-30 17:36 ` Thomas Huth
2018-05-02 7:33 ` Cornelia Huck
2018-05-02 7:43 ` Liviu Ionescu
2018-05-02 7:59 ` Daniel P. Berrangé
2018-05-02 8:02 ` Liviu Ionescu
2018-05-02 8:13 ` Thomas Huth
2018-05-02 9:03 ` Liviu Ionescu
2018-05-02 9:10 ` Daniel P. Berrangé
2018-05-28 9:24 ` Paolo Bonzini
2018-05-02 9:21 ` Cornelia Huck
2018-05-02 9:22 ` Thomas Huth
2018-05-02 8:26 ` Cornelia Huck
2018-05-04 17:34 ` Max Reitz
2018-05-02 7:44 ` Gerd Hoffmann
2018-05-02 8:02 ` Daniel P. Berrangé
2018-05-03 7:21 ` Stefan Hajnoczi
2018-05-03 9:07 ` Daniel P. Berrangé [this message]
2018-05-03 9:26 ` Cornelia Huck
2018-05-03 9:26 ` Peter Maydell
2018-05-03 9:31 ` Daniel P. Berrangé
2018-05-03 9:47 ` Thomas Huth
2018-05-03 13:43 ` Gerd Hoffmann
2018-05-03 14:06 ` Thomas Huth
2018-05-03 14:16 ` Daniel P. Berrangé
2018-05-07 13:38 ` Kashyap Chamarthy
2018-05-07 16:51 ` Thomas Huth
2018-05-03 14:16 ` Cornelia Huck
2018-05-04 13:20 ` Kevin Wolf
2018-05-04 13:53 ` Thomas Huth
2018-05-04 14:23 ` Kevin Wolf
2018-05-04 17:30 ` Richard Henderson
2018-05-07 5:33 ` Thomas Huth
2018-05-07 14:05 ` Kevin Wolf
2018-05-22 10:07 ` Peter Maydell
2018-06-01 11:57 ` Daniel P. Berrangé
2018-04-30 14:23 ` Greg Kurz
2018-04-30 14:30 ` Peter Maydell
2018-04-30 14:34 ` Daniel P. Berrangé
2018-05-03 1:04 ` David Gibson
2018-05-01 12:24 ` Stefan Hajnoczi
2018-05-01 12:48 ` Peter Maydell
2018-05-03 21:52 ` Laurent Vivier
2018-05-04 8:40 ` Stefan Hajnoczi
2018-05-28 5:31 ` Philippe Mathieu-Daudé
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=20180503090727.GC11382@redhat.com \
--to=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=kraxel@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
/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).