I'm supportive of changing the versioning to something without the leading zero in the next release where this is practical. If it's the one after 0.23.0, then I would go with 24.0. IMO, going with 1.0 would send a message that this is the first mature release. But that isn't the case: we have been doing mature releases for a long time now. Going with 24.0 is clearer in that regard.
Happy to repeat this opinion on a new thread too :) On Thu, May 26, 2022 at 6:49 PM Frank Chen <frankc...@apache.org> wrote: > For 0.23, I don't think we need to make changes because I think it may take > us some time to reach an agreement on the naming. > > We can start a new thread to discuss the versioning schema. > > > On Thu, May 26, 2022 at 8:19 PM Abhishek Agarwal < > abhishek.agar...@imply.io> > wrote: > > > We should definitely move away from the `0.xx` versioning scheme we have > > been using. However, the next version that we pick up is debatable. > `23.x` > > seems an odd jump from `0.23`. Can we increment the version to `1.x` > maybe? > > I also like the idea of using Yeah and Month that Frank has suggested. > > > > I don't think that 0.23 is the right release to make this change though. > > 0.23 has already been delayed because of CVE investigations and bug > fixes. > > I would like to get this release out of the door as soon as possible. > > > > On Thu, May 26, 2022 at 2:40 PM Frank Chen <frankc...@apache.org> wrote: > > > > > I agree. > > > > > > This is also a question that I want to ask why the version is still > 0.xx > > > which gives many people a hint that Druid is still under mature. > > > > > > There are many versioning schemas. One popular way is combining the > > release > > > year and month in the version. > > > For example, if we're going to release a version in May this year, the > > main > > > version can be 22.5. > > > > > > > > > Versioning is one thing, LTS strategy should also be clear. > > > Since we're going to release several versions a year, we should plan in > > > advance which one should be scheduled as a LTS version and maintain it > > for > > > a period of time if there are some vital bugs and security issues. > > > > > > > > > > > > > > > On Thu, May 26, 2022 at 1:21 PM Suneet Saldanha <sun...@apache.org> > > wrote: > > > > > > > Hi all, > > > > > > > > I've been thinking that we should consider re-branding this release > as > > > > the Druid 23.0 instead of 0.23 release. I think this is appropriate > > > because > > > > typically a `0.XX` software version implies that the software is in > > it's > > > > infancy. > > > > > > > > Druid is quite mature, and we've been putting good guardrails in > place > > to > > > > detect and prevent breaking API changes in each release. Druid has > also > > > > been running in production clusters for many different use cases for > > > quite > > > > some > > > > time now. I think version 23.0 is more in line with the maturity of > the > > > > project. > > > > > > > > Is there a reason not to change the version for the next release? Any > > > > other thoughts? > > > > > > > > On 2022/04/11 10:21:11 Abhishek Agarwal wrote: > > > > > Thank you for creating that PR, Frank. In the last release, we > > excluded > > > > > helm charts since we were not sure about IP clearance. From > > > > > https://incubator.apache.org/ip-clearance/, we should decide on IP > > > > > clearance whether we include helm charts in artifacts or not. Any > > > > thoughts? > > > > > > > > > > On Wed, Mar 30, 2022 at 4:44 PM Frank Chen <frankc...@apache.org> > > > wrote: > > > > > > > > > > > Hi Abhishek, > > > > > > > > > > > > Thank you for starting the release work. > > > > > > > > > > > > This PR should be merged to address a problem caused by a > previous > > > PR: > > > > > > https://github.com/apache/druid/pull/12067 > > > > > > I've added it to the 0.23 milestone. > > > > > > > > > > > > > > > > > > Thank you. > > > > > > > > > > > > > > > > > > On Wed, Mar 30, 2022 at 2:15 PM Abhishek Agarwal < > > > > > > abhishek.agar...@imply.io> > > > > > > wrote: > > > > > > > > > > > > > Hello everyone, > > > > > > > It's time to kick-off the process for druid 0.23 release. I > will > > > need > > > > > > help > > > > > > > from the community in surfacing any important issues that need > to > > > be > > > > > > > addressed before 0.23 release. We can use this thread to > discuss > > > > those > > > > > > > issues and take a call on how to unblock the release. > > > > > > > > > > > > > > I have also created 0.23 milestone ( > > > > > > > https://github.com/apache/druid/milestone/45). Any issues that > > we > > > > must > > > > > > > want > > > > > > > to fix in the 0.23 release, can be tagged with this milestone. > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: dev-unsubscr...@druid.apache.org > > > > For additional commands, e-mail: dev-h...@druid.apache.org > > > > > > > > > > > > > >
