> If we simply used CassandraVersion (which is broadly equivalent, but
> standard’s compliant)
Actually it’s got the same issue, but it’s a one line fix.
From: Mick Semb Wever <m...@apache.org>
Date: Tuesday, 21 December 2021 at 22:06
To:
Cc: dev@cassandra.apache.org <dev@cassandra.apache.org>
Subject: Re: [DISCUSS] Periodic snapshot publishing with minor version bumps
> These can be further subdivided to:
>
> A1. 4.1.0-PRE{1,2,3,4} -> 4.1.0-alpha1
> A2. 4.1.0-alpha{1,2,3,4} -> 4.1.0-alpha5
> B1. 4.1.{0,1,2,3} -> 4.1.4-alpha1
> B2. 4.{1,2,3,4} -> 4.5.0-alpha1
> B3. 4.{1,2,3,4} -> 5.0.0-alpha1
> C1. 4.1.{0,1,2,3}-pre -> 4.1.4-alpha1
> C2. 4.{1,2,3,4}.0-pre -> 4.5.0-alpha1
> C3. 4.{1,2,3,4}.0-pre -> 5.0.0-alpha1
>
(A) does not work with the codebase as it is today. It requires additional work.
(B) has not been suggested anywhere in the thread, so I find it odd
that it was proposed.
(C2) is the original proposal. (Though the build metadata suffix is
not "pre", it is either SNAPSHOT or a timestamp.)
(B3) and (C3) doesn't follow SemVer.
(C1) is interesting, I wouldn't object to it, though share similar
initial reaction to Josh.
