Re: Cassandra 4.0 Dev Work Status

2020-01-15 Thread Joshua McKenzie
Historically I believe we used the ".x" nomenclature to indicate general release we wanted things in (4.x, 3.11.x, 3.6.x, etc), and then upon merge update the FixVersion to reflect which release it actually went in. Is that still a thing, and whether a thing or not, is the current appropriate usage

Re: Cassandra 4.0 Dev Work Status

2020-01-15 Thread Benedict Elliott Smith
I think there's always been a distinction in the way we treat alphas/betas versus patch releases, because they have a staged delivery (landing for dev and users in different releases). I don't know we've ever been totally consistent about it across major versions though. I think we can view 4.

Re: Cassandra 4.0 Dev Work Status

2020-01-15 Thread Benedict Elliott Smith
Specifically, if anyone's interested, I think we should probably maintain three tags for work landing in 4.0, e.g. 4.0-alpha1, 4.0-alpha, 4.0 This helps track all of the relevant information, the first limited release, the first general release, and the point in the release process it was deliv