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 the next release be called? 25.0? If that is the case, then the number means nothing, every release is a major version and nothing has changed from what it is today except moving a decimal point. Personally I think we should focus on what we are going to do going forward for druid users such that they can be assured that compatibility is met between releases. Right now it is release notes, but if we start using minor versioning like it is intended - that would be much more clear. On Fri, May 27, 2022 at 9:25 AM suneet Saldanha <sun...@apache.org> wrote: > 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 [1]. > > Other ideas that were proposed > * Use a year / month in the release > * Make the next release 1.xx > > I think the year month is interesting, but since we do not have a planned > release schedule, > it is hard to pick the version that should be in the `master` branch while > active dev is happening. > > Labeling the next release as 1.xx makes it appear as if the current version > of Druid isn't very > stable since the current version is 0.xx which isn't the case. > > Happy to hear more opinions on this so we can get to consensus before it is > time for the next code freeze + release. > > [1] > > https://lists.apache.org/list?dev@druid.apache.org:2022-5:[DISCUSS]%20Druid%200.23%20release >
