> Vendors are also free to support and provide hot-fixes and back ports on
> these unreleased versions, outside of the community's efforts or concerns
This seems to me like we're endorsing the release of these versions by
downstream maintainers? Even if we decide to modify this proposal and say "no,
we don't endorse that," how do we prevent it?
What's the benefit of this approach over using snapshot tags, if the goal is
just making downstream maintainer's lives easier wrt merging a year's worth of
work?
On 03/05/2021, 10:09, "Mick Semb Wever" <m...@apache.org> wrote:
> Well the other problem I see is that this could create a lot of confusion
for our users, if more versions start popping up (and/or versions are skipped).
It's hard to row back from unwanted versions in the wild, and we may end up
having to either support them or disappoint our users.
This is not made explicit to users. Not through announcements or
formal releases. This is strictly within dev.
Any bugs reported back upstream to the community in the dev cycle will
be fixed in trunk, that's the stated dev cycle and we don't deviate.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org
