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
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
What about a 1.0 release? I think there is no backwards compatibility promised
until Druid gets to 1.0+. I think it would be really helpful to customers to
start making upgrades rollable and guaranteeing compatibility between minor
versions. Any plans for this to happen in the near future?
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
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
wrote:
> We should definitely move away from the `0.xx`
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
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
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
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
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
wrote:
> Hello everyone,
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
11 matches
Mail list logo
