Having a baseline is important and shipping
e.g. "Eclipse 2016 Update 3" in February 2017 would be very confusing.
Currently we label the release with
a name and a version, e.g. Neon (4.6). Another solution would be to keep
the name and replace the version with the date, e.g. Neon (06/2016) and
Neon.1 (09/2016) and Neon.3 (02/2017).
Bruno Medeiros <bruno.do.medeiros@xxxxxxxxx> To:
Discussions about the
IDE <ide-dev@xxxxxxxxxxx> Date:
29.04.2016 12:06 Subject:
Dropping the release names (Neon, Oxygen)
from user downloads Sent by:
On 29 April 2016 at 09:58, Lars Vogel <lars.vogel@xxxxxxxxxxx>
wrote: Gunnar, Platform may also change their policy over time
so you should not pick a schema that assumes Platform will forever work
I'm with Gunnar on this one. If the release structure/rhythm
changes, we can always change the versioning again to better suit the new
release structure. But not the other way around, we shouldn't change
to a versioning scheme that doesn't suit the current release structure.
Your suggestion of having a real date like "16.10" makes it totally
unclear if it is a major release or a minor one.