t 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
this opinion on a new thread too :)
> >
> >> On Thu, May 26, 2022 at 6:49 PM Frank Chen 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.
> >>
>
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
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 wrote:
> For 0.23, I don't think we need to make changes because I think it may take
> us some time to
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
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
vital bugs and security issues.
On Thu, May 26, 2022 at 1:21 PM Suneet Saldanha 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
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
at 4:44 PM Frank Chen 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.
>
Hi Baris
I don't see an attachment in your email.
On Sat, Apr 9, 2022 at 5:38 AM Baris Dogan wrote:
> Hi,
>
> Could you just put the following CVE findings (attached into the email)
> into the next release scope which come out of trivy 0.23 tests.
>
> On 2022/03/25 03:52:50
Hi,
Could you just put the following CVE findings (attached into the email)
into the next release scope which come out of trivy 0.23 tests.
On 2022/03/25 03:52:50 Gian Merlino wrote:
> I agree it's a good time to do a release. Most of the release-manager
steps
> involve having commit priv
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 every
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
Thank you! Much appreciated.
On Mon, Mar 28, 2022 at 7:58 AM Abhishek Agarwal
wrote:
> Hi Eyal
> Thanks for bringing this up. I am going to volunteer for shepherding 0.23
> release. I will start a new thread soon.
>
> On Fri, Mar 25, 2022 at 9:23 AM Gian Merlino wrote:
>
>
Hi Eyal
Thanks for bringing this up. I am going to volunteer for shepherding 0.23
release. I will start a new thread soon.
On Fri, Mar 25, 2022 at 9:23 AM Gian Merlino wrote:
> I agree it's a good time to do a release. Most of the release-manager steps
> involve having commit priv
plan to work on releasing 0.23?
> I'll be really glad to manage the 0.23 release but I'm not a committer.
> Assuming this requires committer privileges, I'd be glad if anyone can
> volunteer.
>
> BTW, have you noticed that we shifted away from the official quarterly
> releases
Hi,
Anyone plan to work on releasing 0.23?
I'll be really glad to manage the 0.23 release but I'm not a committer.
Assuming this requires committer privileges, I'd be glad if anyone can
volunteer.
BTW, have you noticed that we shifted away from the official quarterly
releases? Perhaps we should
17 matches
Mail list logo
