You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@drill.apache.org by James Turton <dz...@apache.org> on 2022/01/29 12:36:51 UTC
[VOTE] Freeze for Drill 1.20
Hello Dev community
Not a moment too soon, we've finally dispatched the last issues holding
back 1.20! Here's a big thank you from the release manager to everyone
who helped to push us forward to this point. I'm sure I'm not the only
one receiving the "When it's coming??" questions. As an interesting bit
of trivia, there have been about 9 months separating recent releases and
it has now been about 8 months since 1.19. Who knew we were so
consistent ;-) ?
Please vote for or against a feature freeze on the master branch. I
assume only critical bug or vulnerability fixes get freeze immunity?
Thank you
James
Re: [VOTE] Freeze for Drill 1.20
Posted by Charles Givre <cg...@gmail.com>.
Great work James! Thanks everyone for all the work that goes into the release! We’re almost there!
— C
> On Feb 3, 2022, at 8:30 AM, James Turton <ja...@somecomputer.xyz.INVALID> wrote:
>
> Great, thanks everyone. I've started preparing a release candidate.
>
> Please do not merge anything into the master branch from now until we're clear.
>
> James
>
>
> On 2022/02/02 20:18, Z0ltrix wrote:
>> +1 from me
>>
>> Regards
>> Christian
>>
>>
>>
>> -------- Original-Nachricht --------
>> Am 2. Feb. 2022, 17:13, Vitalii Diravka schrieb:
>>
>>
>> +1
>>
>> Kind regards
>> Vitalii
>>
>> On Wed, Feb 2, 2022 at 6:04 PM Vova Vysotskyi
>> <vo...@apache.org> wrote:
>>
>> > +1
>> >
>> > Kind regards,
>> > Volodymyr Vysotskyi
>> >
>> > On 2022/02/02 15:59:55 James Turton wrote:
>> > > PR #2449 was merged and there are now zero Dependabot alerts
>> against
>> > > master.
>> > >
>> > > +1 for freezing from me.
>> > >
>> > > On 2022/02/02 16:36, Charles Givre wrote:
>> > > > Assuming we pass dependabot, big +1 from me!! Great work
>> everyone!
>> > > > --C
>> > > >
>> > > >> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org>
>> wrote:
>> > > >>
>> > > >> Please vote again on the assumption that the very minor
>> Postgresql
>> > 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot
>> alert. It
>> > passed local testing so it looks like a safe bet.
>> > > >>
>> > > >>
>> > > >> On 2022/01/30 01:51, Charles Givre wrote:
>> > > >>> Hey James,
>> > > >>> Alas... I'm afraid I'd have to give a -1 on this. There
>> are some
>> > dependabot alerts at the moment, which we really should resolve
>> (or at
>> > least look at) before cutting a release. One of which has is
>> linked to a
>> > severe CVE. Also, I just submitted a VERY minor bug fix which
>> I'd love to
>> > squeak into this release, but that's not urgent.
>> > > >>> Best,
>> > > >>> --C
>> > > >>>
>> > > >>>
>> > > >>>> On Jan 29, 2022, at 7:36 AM, James Turton
>> <dz...@apache.org> wrote:
>> > > >>>>
>> > > >>>> Hello Dev community
>> > > >>>>
>> > > >>>> Not a moment too soon, we've finally dispatched the last
>> issues
>> > holding back 1.20! Here's a big thank you from the release
>> manager to
>> > everyone who helped to push us forward to this point. I'm sure
>> I'm not the
>> > only one receiving the "When it's coming??" questions. As an
>> interesting
>> > bit of trivia, there have been about 9 months separating recent
>> releases
>> > and it has now been about 8 months since 1.19. Who knew we were so
>> > consistent ;-) ?
>> > > >>>>
>> > > >>>> Please vote for or against a feature freeze on the master
>> branch.
>> > I assume only critical bug or vulnerability fixes get freeze
>> immunity?
>> > > >>>>
>> > > >>>> Thank you
>> > > >>>> James
>> > > >>>>
>> > > >>
>> > > >
>> > >
>> >
>>
Re: [VOTE] Freeze for Drill 1.20
Posted by James Turton <ja...@somecomputer.xyz.INVALID>.
Great, thanks everyone. I've started preparing a release candidate.
Please do not merge anything into the master branch from now until we're
clear.
James
On 2022/02/02 20:18, Z0ltrix wrote:
> +1 from me
>
> Regards
> Christian
>
>
>
> -------- Original-Nachricht --------
> Am 2. Feb. 2022, 17:13, Vitalii Diravka schrieb:
>
>
> +1
>
> Kind regards
> Vitalii
>
> On Wed, Feb 2, 2022 at 6:04 PM Vova Vysotskyi
> <vo...@apache.org> wrote:
>
> > +1
> >
> > Kind regards,
> > Volodymyr Vysotskyi
> >
> > On 2022/02/02 15:59:55 James Turton wrote:
> > > PR #2449 was merged and there are now zero Dependabot alerts
> against
> > > master.
> > >
> > > +1 for freezing from me.
> > >
> > > On 2022/02/02 16:36, Charles Givre wrote:
> > > > Assuming we pass dependabot, big +1 from me!! Great work
> everyone!
> > > > --C
> > > >
> > > >> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org>
> wrote:
> > > >>
> > > >> Please vote again on the assumption that the very minor
> Postgresql
> > 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot
> alert. It
> > passed local testing so it looks like a safe bet.
> > > >>
> > > >>
> > > >> On 2022/01/30 01:51, Charles Givre wrote:
> > > >>> Hey James,
> > > >>> Alas... I'm afraid I'd have to give a -1 on this. There
> are some
> > dependabot alerts at the moment, which we really should resolve
> (or at
> > least look at) before cutting a release. One of which has is
> linked to a
> > severe CVE. Also, I just submitted a VERY minor bug fix which
> I'd love to
> > squeak into this release, but that's not urgent.
> > > >>> Best,
> > > >>> --C
> > > >>>
> > > >>>
> > > >>>> On Jan 29, 2022, at 7:36 AM, James Turton
> <dz...@apache.org> wrote:
> > > >>>>
> > > >>>> Hello Dev community
> > > >>>>
> > > >>>> Not a moment too soon, we've finally dispatched the last
> issues
> > holding back 1.20! Here's a big thank you from the release
> manager to
> > everyone who helped to push us forward to this point. I'm sure
> I'm not the
> > only one receiving the "When it's coming??" questions. As an
> interesting
> > bit of trivia, there have been about 9 months separating recent
> releases
> > and it has now been about 8 months since 1.19. Who knew we were so
> > consistent ;-) ?
> > > >>>>
> > > >>>> Please vote for or against a feature freeze on the master
> branch.
> > I assume only critical bug or vulnerability fixes get freeze
> immunity?
> > > >>>>
> > > >>>> Thank you
> > > >>>> James
> > > >>>>
> > > >>
> > > >
> > >
> >
>
Re: [VOTE] Freeze for Drill 1.20
Posted by Z0ltrix <z0...@pm.me.INVALID>.
\+1 from me
Regards
Christian
\-------- Original-Nachricht --------
Am 2. Feb. 2022, 17:13, Vitalii Diravka schrieb:
>
>
>
> \+1
>
> Kind regards
> Vitalii
>
>
> On Wed, Feb 2, 2022 at 6:04 PM Vova Vysotskyi <vo...@apache.org> wrote:
>
> > +1
> >
> > Kind regards,
> > Volodymyr Vysotskyi
> >
> > On 2022/02/02 15:59:55 James Turton wrote:
> > > PR \#2449 was merged and there are now zero Dependabot alerts against
> > > master.
> > >
> > > +1 for freezing from me.
> > >
> > > On 2022/02/02 16:36, Charles Givre wrote:
> > > > Assuming we pass dependabot, big +1 from me!! Great work everyone!
> > > > --C
> > > >
> > > >> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org> wrote:
> > > >>
> > > >> Please vote again on the assumption that the very minor Postgresql
> > 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot alert. It
> > passed local testing so it looks like a safe bet.
> > > >>
> > > >>
> > > >> On 2022/01/30 01:51, Charles Givre wrote:
> > > >>> Hey James,
> > > >>> Alas... I'm afraid I'd have to give a -1 on this. There are some
> > dependabot alerts at the moment, which we really should resolve (or at
> > least look at) before cutting a release. One of which has is linked to a
> > severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to
> > squeak into this release, but that's not urgent.
> > > >>> Best,
> > > >>> --C
> > > >>>
> > > >>>
> > > >>>> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
> > > >>>>
> > > >>>> Hello Dev community
> > > >>>>
> > > >>>> Not a moment too soon, we've finally dispatched the last issues
> > holding back 1.20! Here's a big thank you from the release manager to
> > everyone who helped to push us forward to this point. I'm sure I'm not the
> > only one receiving the "When it's coming??" questions. As an interesting
> > bit of trivia, there have been about 9 months separating recent releases
> > and it has now been about 8 months since 1.19. Who knew we were so
> > consistent ;-) ?
> > > >>>>
> > > >>>> Please vote for or against a feature freeze on the master branch.
> > I assume only critical bug or vulnerability fixes get freeze immunity?
> > > >>>>
> > > >>>> Thank you
> > > >>>> James
> > > >>>>
> > > >>
> > > >
> > >
> >
>
Re: [VOTE] Freeze for Drill 1.20
Posted by Vitalii Diravka <vi...@apache.org>.
+1
Kind regards
Vitalii
On Wed, Feb 2, 2022 at 6:04 PM Vova Vysotskyi <vo...@apache.org> wrote:
> +1
>
> Kind regards,
> Volodymyr Vysotskyi
>
> On 2022/02/02 15:59:55 James Turton wrote:
> > PR #2449 was merged and there are now zero Dependabot alerts against
> > master.
> >
> > +1 for freezing from me.
> >
> > On 2022/02/02 16:36, Charles Givre wrote:
> > > Assuming we pass dependabot, big +1 from me!! Great work everyone!
> > > --C
> > >
> > >> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org> wrote:
> > >>
> > >> Please vote again on the assumption that the very minor Postgresql
> 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot alert. It
> passed local testing so it looks like a safe bet.
> > >>
> > >>
> > >> On 2022/01/30 01:51, Charles Givre wrote:
> > >>> Hey James,
> > >>> Alas... I'm afraid I'd have to give a -1 on this. There are some
> dependabot alerts at the moment, which we really should resolve (or at
> least look at) before cutting a release. One of which has is linked to a
> severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to
> squeak into this release, but that's not urgent.
> > >>> Best,
> > >>> --C
> > >>>
> > >>>
> > >>>> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
> > >>>>
> > >>>> Hello Dev community
> > >>>>
> > >>>> Not a moment too soon, we've finally dispatched the last issues
> holding back 1.20! Here's a big thank you from the release manager to
> everyone who helped to push us forward to this point. I'm sure I'm not the
> only one receiving the "When it's coming??" questions. As an interesting
> bit of trivia, there have been about 9 months separating recent releases
> and it has now been about 8 months since 1.19. Who knew we were so
> consistent ;-) ?
> > >>>>
> > >>>> Please vote for or against a feature freeze on the master branch.
> I assume only critical bug or vulnerability fixes get freeze immunity?
> > >>>>
> > >>>> Thank you
> > >>>> James
> > >>>>
> > >>
> > >
> >
>
Re: [VOTE] Freeze for Drill 1.20
Posted by Vova Vysotskyi <vo...@apache.org>.
+1
Kind regards,
Volodymyr Vysotskyi
On 2022/02/02 15:59:55 James Turton wrote:
> PR #2449 was merged and there are now zero Dependabot alerts against
> master.
>
> +1 for freezing from me.
>
> On 2022/02/02 16:36, Charles Givre wrote:
> > Assuming we pass dependabot, big +1 from me!! Great work everyone!
> > --C
> >
> >> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org> wrote:
> >>
> >> Please vote again on the assumption that the very minor Postgresql 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot alert. It passed local testing so it looks like a safe bet.
> >>
> >>
> >> On 2022/01/30 01:51, Charles Givre wrote:
> >>> Hey James,
> >>> Alas... I'm afraid I'd have to give a -1 on this. There are some dependabot alerts at the moment, which we really should resolve (or at least look at) before cutting a release. One of which has is linked to a severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to squeak into this release, but that's not urgent.
> >>> Best,
> >>> --C
> >>>
> >>>
> >>>> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
> >>>>
> >>>> Hello Dev community
> >>>>
> >>>> Not a moment too soon, we've finally dispatched the last issues holding back 1.20! Here's a big thank you from the release manager to everyone who helped to push us forward to this point. I'm sure I'm not the only one receiving the "When it's coming??" questions. As an interesting bit of trivia, there have been about 9 months separating recent releases and it has now been about 8 months since 1.19. Who knew we were so consistent ;-) ?
> >>>>
> >>>> Please vote for or against a feature freeze on the master branch. I assume only critical bug or vulnerability fixes get freeze immunity?
> >>>>
> >>>> Thank you
> >>>> James
> >>>>
> >>
> >
>
Re: [VOTE] Freeze for Drill 1.20
Posted by James Turton <dz...@apache.org>.
PR #2449 was merged and there are now zero Dependabot alerts against
master.
+1 for freezing from me.
On 2022/02/02 16:36, Charles Givre wrote:
> Assuming we pass dependabot, big +1 from me!! Great work everyone!
> --C
>
>> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org> wrote:
>>
>> Please vote again on the assumption that the very minor Postgresql 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot alert. It passed local testing so it looks like a safe bet.
>>
>>
>> On 2022/01/30 01:51, Charles Givre wrote:
>>> Hey James,
>>> Alas... I'm afraid I'd have to give a -1 on this. There are some dependabot alerts at the moment, which we really should resolve (or at least look at) before cutting a release. One of which has is linked to a severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to squeak into this release, but that's not urgent.
>>> Best,
>>> --C
>>>
>>>
>>>> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
>>>>
>>>> Hello Dev community
>>>>
>>>> Not a moment too soon, we've finally dispatched the last issues holding back 1.20! Here's a big thank you from the release manager to everyone who helped to push us forward to this point. I'm sure I'm not the only one receiving the "When it's coming??" questions. As an interesting bit of trivia, there have been about 9 months separating recent releases and it has now been about 8 months since 1.19. Who knew we were so consistent ;-) ?
>>>>
>>>> Please vote for or against a feature freeze on the master branch. I assume only critical bug or vulnerability fixes get freeze immunity?
>>>>
>>>> Thank you
>>>> James
>>>>
>>
>
Re: [VOTE] Freeze for Drill 1.20
Posted by James Turton <dz...@apache.org>.
PR #2449 was merged and there are now zero Dependabot alerts against
master.
+1 for freezing from me.
On 2022/02/02 16:36, Charles Givre wrote:
> Assuming we pass dependabot, big +1 from me!! Great work everyone!
> --C
>
>> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org> wrote:
>>
>> Please vote again on the assumption that the very minor Postgresql 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot alert. It passed local testing so it looks like a safe bet.
>>
>>
>> On 2022/01/30 01:51, Charles Givre wrote:
>>> Hey James,
>>> Alas... I'm afraid I'd have to give a -1 on this. There are some dependabot alerts at the moment, which we really should resolve (or at least look at) before cutting a release. One of which has is linked to a severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to squeak into this release, but that's not urgent.
>>> Best,
>>> --C
>>>
>>>
>>>> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
>>>>
>>>> Hello Dev community
>>>>
>>>> Not a moment too soon, we've finally dispatched the last issues holding back 1.20! Here's a big thank you from the release manager to everyone who helped to push us forward to this point. I'm sure I'm not the only one receiving the "When it's coming??" questions. As an interesting bit of trivia, there have been about 9 months separating recent releases and it has now been about 8 months since 1.19. Who knew we were so consistent ;-) ?
>>>>
>>>> Please vote for or against a feature freeze on the master branch. I assume only critical bug or vulnerability fixes get freeze immunity?
>>>>
>>>> Thank you
>>>> James
>>>>
>>
>
Re: [VOTE] Freeze for Drill 1.20
Posted by Charles Givre <cg...@gmail.com>.
Assuming we pass dependabot, big +1 from me!! Great work everyone!
--C
> On Feb 2, 2022, at 9:35 AM, James Turton <dz...@apache.org> wrote:
>
> Please vote again on the assumption that the very minor Postgresql 42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot alert. It passed local testing so it looks like a safe bet.
>
>
> On 2022/01/30 01:51, Charles Givre wrote:
>> Hey James,
>> Alas... I'm afraid I'd have to give a -1 on this. There are some dependabot alerts at the moment, which we really should resolve (or at least look at) before cutting a release. One of which has is linked to a severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to squeak into this release, but that's not urgent.
>> Best,
>> --C
>>
>>
>>> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
>>>
>>> Hello Dev community
>>>
>>> Not a moment too soon, we've finally dispatched the last issues holding back 1.20! Here's a big thank you from the release manager to everyone who helped to push us forward to this point. I'm sure I'm not the only one receiving the "When it's coming??" questions. As an interesting bit of trivia, there have been about 9 months separating recent releases and it has now been about 8 months since 1.19. Who knew we were so consistent ;-) ?
>>>
>>> Please vote for or against a feature freeze on the master branch. I assume only critical bug or vulnerability fixes get freeze immunity?
>>>
>>> Thank you
>>> James
>>>
>
Re: [VOTE] Freeze for Drill 1.20
Posted by James Turton <dz...@apache.org>.
Please vote again on the assumption that the very minor Postgresql
42.3.1 -> 42.3.2 PR will be merged, clearing the last Dependabot alert.
It passed local testing so it looks like a safe bet.
On 2022/01/30 01:51, Charles Givre wrote:
> Hey James,
> Alas... I'm afraid I'd have to give a -1 on this. There are some dependabot alerts at the moment, which we really should resolve (or at least look at) before cutting a release. One of which has is linked to a severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to squeak into this release, but that's not urgent.
> Best,
> --C
>
>
>> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
>>
>> Hello Dev community
>>
>> Not a moment too soon, we've finally dispatched the last issues holding back 1.20! Here's a big thank you from the release manager to everyone who helped to push us forward to this point. I'm sure I'm not the only one receiving the "When it's coming??" questions. As an interesting bit of trivia, there have been about 9 months separating recent releases and it has now been about 8 months since 1.19. Who knew we were so consistent ;-) ?
>>
>> Please vote for or against a feature freeze on the master branch. I assume only critical bug or vulnerability fixes get freeze immunity?
>>
>> Thank you
>> James
>>
Re: [VOTE] Freeze for Drill 1.20
Posted by James Turton <dz...@apache.org>.
In addition to the vulnerable dependencies, of which H2 does not upgrade
cleanly, there is now another new release blocker:
DRILL-8119 - MongoDB query regression: mem leak and data type error
<https://issues.apache.org/jira/browse/DRILL-8119>
Regards
James
On 2022/01/30 01:51, Charles Givre wrote:
> Hey James,
> Alas... I'm afraid I'd have to give a -1 on this. There are some dependabot alerts at the moment, which we really should resolve (or at least look at) before cutting a release. One of which has is linked to a severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to squeak into this release, but that's not urgent.
> Best,
> --C
>
>
>> On Jan 29, 2022, at 7:36 AM, James Turton<dz...@apache.org> wrote:
>>
>> Hello Dev community
>>
>> Not a moment too soon, we've finally dispatched the last issues holding back 1.20! Here's a big thank you from the release manager to everyone who helped to push us forward to this point. I'm sure I'm not the only one receiving the "When it's coming??" questions. As an interesting bit of trivia, there have been about 9 months separating recent releases and it has now been about 8 months since 1.19. Who knew we were so consistent ;-) ?
>>
>> Please vote for or against a feature freeze on the master branch. I assume only critical bug or vulnerability fixes get freeze immunity?
>>
>> Thank you
>> James
>>
Re: [VOTE] Freeze for Drill 1.20
Posted by Charles Givre <cg...@gmail.com>.
Hey James,
Alas... I'm afraid I'd have to give a -1 on this. There are some dependabot alerts at the moment, which we really should resolve (or at least look at) before cutting a release. One of which has is linked to a severe CVE. Also, I just submitted a VERY minor bug fix which I'd love to squeak into this release, but that's not urgent.
Best,
--C
> On Jan 29, 2022, at 7:36 AM, James Turton <dz...@apache.org> wrote:
>
> Hello Dev community
>
> Not a moment too soon, we've finally dispatched the last issues holding back 1.20! Here's a big thank you from the release manager to everyone who helped to push us forward to this point. I'm sure I'm not the only one receiving the "When it's coming??" questions. As an interesting bit of trivia, there have been about 9 months separating recent releases and it has now been about 8 months since 1.19. Who knew we were so consistent ;-) ?
>
> Please vote for or against a feature freeze on the master branch. I assume only critical bug or vulnerability fixes get freeze immunity?
>
> Thank you
> James
>
Re: [VOTE] Freeze for Drill 1.20
Posted by Z0ltrix <z0...@pm.me.INVALID>.
I've been eagerly awaiting the release with the Phoenix connection, so i would like to see the feature freeze.
Regards
Christian
\-------- Original-Nachricht --------
Am 29. Jan. 2022, 13:36, James Turton schrieb:
>
>
>
> Hello Dev community
>
> Not a moment too soon, we've finally dispatched the last issues holding
> back 1.20! Here's a big thank you from the release manager to everyone
> who helped to push us forward to this point. I'm sure I'm not the only
> one receiving the "When it's coming??" questions. As an interesting bit
> of trivia, there have been about 9 months separating recent releases and
> it has now been about 8 months since 1.19. Who knew we were so
> consistent ;-) ?
>
> Please vote for or against a feature freeze on the master branch. I
> assume only critical bug or vulnerability fixes get freeze immunity?
>
> Thank you
> James