[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] release retrospective, next release timing, numbering

From: Thomas Huth
Subject: Re: [Qemu-devel] release retrospective, next release timing, numbering
Date: Mon, 7 May 2018 18:51:01 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0

On 07.05.2018 15:38, Kashyap Chamarthy wrote:
> On Thu, May 03, 2018 at 03:16:10PM +0100, Daniel P. Berrangé wrote:
>> On Thu, May 03, 2018 at 04:06:19PM +0200, Thomas Huth wrote:
>>> On 03.05.2018 15:43, Gerd Hoffmann wrote:
> [...]
>>>>   (a) major equals year, minor equals month (ubuntu style).
>>>>   (b) major equals year, minor counts up (mesa style).
>>>>   (c) major is bumped each year, but doesn't equal year (libvirt style).
>>>> If we don't want give them a meaning, how about:
>>>>   (d) just drop the minor and count up major each release (systemd style)?
>>>> My personal preference would be (a) or (b), because it is easy to see
>>>> when a version was released.  (b) looks more like a classic version
>>>> number, we would have 18.0, 18.1, ... instead of 18.04, 18.08, ...
>>> I'd really would like to avoid variant (a) ... otherwise people will
>>> confuse 18.1.1 and 18.11 (aka. 18.11.0) again...
>> We could keep major == year, minor == nth release of $year. eg 18.1,
>> 18.2, 18.3 for the 1st, 2nd and 3rd releases of 2018. Still makes it
>> fairly clear what timeframe each was released in, without having to
>> follow month numbers.
> FWIW, the above option sounds simplest to explain so far.

No, there are some drawbacks when the major version equals the year, see





reply via email to

[Prev in Thread] Current Thread [Next in Thread]