Yeah, I'd say the next one after 24.0 would be 25.0. The idea is really
just to remove the leading zero and thereby communicate the accurate state
of the project: it has been stable and production-ready for a long time.
Some people see the leading zero and interpret that as a sign of an
immature
I would say that semantic versioning for me is very important for
determining compatibility between releases. Minor versions should always
adhere to being compatible with each other and a major version bump is
where you can potentially break it.
Right now calling it 24.0 is fine, but what would
Thank you, Suneet.
On Fri, May 27, 2022 at 9:46 PM Suneet Saldanha wrote:
> Agreed. Naming is hard, and I wouldn't want to slow down this release
> trying to get
> consensus on the correct versioning scheme. They all seem to have merits.
> I will start
> another thread to discuss this so we
Hi Druids,
I'd like to propose we bump the version of Druid to 24.0 for the next
release.
I think this would be beneficial because it better reflects the maturity of
the Druid
project that is actively used in many production use cases. This was
discussed briefly
in the Druid 0.23.0 release thread
Agreed. Naming is hard, and I wouldn't want to slow down this release trying to
get
consensus on the correct versioning scheme. They all seem to have merits. I
will start
another thread to discuss this so we will have a decision by the time the next
release
rolls around.
On 2022/05/27 02:57:39
