Re: [DISCUSS] Renumber Groovy 2.6 to 2.9
If you go with 2.9 now, and for unforseeable reasons the 2.x branch
continues, you will have 2.6, 2.7, 2.8 and then the prematurely added
What would you think about any other project versioning like that?
Even with a given explanation, it looks weird and chaotic.
On Tue, May 22, 2018 at 11:12 AM, Paul King <paulk@xxxxxxxxxxxx> wrote:
> 2.6/3.0-- has only undergone alpha releases. The fact that 2.7/2.8 are
> missing and that people stop to think is a good thing.
> We are planning breaking changes for 3 (and hence 2.6/3.0--). With semantic
> versioning, 2.6/3.0-- should not have such changes.
> So it really should be versions 3 and 4 but since we are going to drop
> support for 2.6/3.0-- straight away, it hardly seems worthy
> of a dedicated whole version. I think 2.9 is a good compromise version
> Dropping it altogether is another option but if you remember it was
> non-committer contributors that wanted this change and did
> most of the (original at least) contributions. We've done all the work, I
> say let's just release as 2.9 and then drop it. If outside
> contributors want to continue bug fixes on it, so be it.
> Cheers, Paul.
> On Tue, May 22, 2018 at 1:12 AM, John Wagenleitner
> <john.wagenleitner@xxxxxxxxx> wrote:
>> My opinion is that it should be left as 2.6. Since 2.6 has already
>> undergone several pre-releases I think it will may be more confusing to
>> re-number now. Renumbering may also give the impression that a 2.7 or 2.8
>> might be coming or at least make some wonder what happened to those
>> On Sat, May 19, 2018 at 8:58 PM Paul King <paulk@xxxxxxxxxxxx> wrote:
>>> I was wondering what people thought about renumbering Groovy 2.6 to 2.9.
>>> It is only a subtle change but I think better conveys that it isn't a
>>> small step up
>>> from 2.5 but rather something just a bit short of 3.
>>> Cheers, Paul.