From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fEAa3-0002zG-5u for qemu-devel@nongnu.org; Thu, 03 May 2018 05:31:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fEAZy-0001Yc-VP for qemu-devel@nongnu.org; Thu, 03 May 2018 05:31:15 -0400 Received: from mx3-rdu2.redhat.com ([66.187.233.73]:56036 helo=mx1.redhat.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fEAZy-0001YS-QB for qemu-devel@nongnu.org; Thu, 03 May 2018 05:31:10 -0400 Date: Thu, 3 May 2018 10:31:03 +0100 From: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= Message-ID: <20180503093103.GE11382@redhat.com> Reply-To: Daniel =?utf-8?B?UC4gQmVycmFuZ8Op?= References: <20180430103312.GH3249@redhat.com> <20180430132107.0a37704d.cohuck@redhat.com> <20180502074403.yh5weukbjgqsvp7n@sirius.home.kraxel.org> <20180502080200.GG3308@redhat.com> <20180503072100.GA5301@stefanha-x1.localdomain> <20180503090727.GC11382@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] release retrospective, next release timing, numbering List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Stefan Hajnoczi , Gerd Hoffmann , Thomas Huth , Cornelia Huck , QEMU Developers On Thu, May 03, 2018 at 10:26:40AM +0100, Peter Maydell wrote: > On 3 May 2018 at 10:07, Daniel P. Berrang=C3=A9 w= rote: > > On Thu, May 03, 2018 at 08:21:00AM +0100, Stefan Hajnoczi wrote: > >> 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 version= ing > > amongst people replying here. I'd be happy with YY.MM >=20 > I'm not hugely in favour mostly because I don't much like > changing version numbering formats -- does it really gain > us anything? But I guess it's a bit of a bikeshed-colour question. You mean the change from 3 to 2 digits ? We would presumably need to stick a zero on the end of it anyway. eg 18.04.0 indicates 2018, May initial release. Then 18.04.1 indicates the first stable branch release, etc. Or if you mean you don't like the jump from 2.x to 18.x, we could just follow a time based version scheme, but just bumping major digit once a year as I first suggested in this thread ? Both are effectively saying the same thing - we're changing versions based on time, not features. So it is largely a matter of whether you want the actual date visible or not. Regards, Daniel --=20 |: https://berrange.com -o- https://www.flickr.com/photos/dberran= ge :| |: https://libvirt.org -o- https://fstop138.berrange.c= om :| |: https://entangle-photo.org -o- https://www.instagram.com/dberran= ge :|