You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@calcite.apache.org by Julian Hyde <jh...@gmail.com> on 2020/07/23 17:15:12 UTC

[DISCUSS] Towards Calcite 1.25.0

The release vote for 1.24 RC0 just passed [1], and it will be released shortly.

We planned that release 1.24 is a transitional release, and 1.25 will follow soon afterwards. 1.24 deprecates some APIs that we intend to remove in 1.25. We had to make the release so that people can see that the APIs are deprecated, and replace them with the new versions.

During the release vote we ran into 4136 [2]. This is a real bug, caused in part by the API changes to deprecate APIs (and provide long-term replacements) and in part caused by 4079 [3], the real bug that we are trying to solve in 1.25.

So, it is important that we release 1.25 soon, and that it solves all of these problems. I don’t know whether people will perceive 1.24 as a release “lower than our usual quality” (even though there are good reasons for it) but 1.25 needs to be back to the usual quality.

Julian

[1] https://issues.apache.org/jira/browse/CALCITE-4117 <https://issues.apache.org/jira/browse/CALCITE-4117>

[2] https://issues.apache.org/jira/browse/CALCITE-4136 <https://issues.apache.org/jira/browse/CALCITE-4136>

[3] https://issues.apache.org/jira/browse/CALCITE-4079 <https://issues.apache.org/jira/browse/CALCITE-4079>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Julian Hyde <jh...@apache.org>.

There are several categories of "important":

Breaking: 2569, 3923, 4079.

Highlights: 4134 (interval expressions), 4080 (character literals as
aliases), 3923 (change how planner rules are parameterized); 2160
(spatial functions).

On Sat, Aug 8, 2020 at 1:11 PM Andrei Sereda <an...@sereda.cc> wrote:
>
> I would say yes.
>
> On Sat, Aug 8, 2020, 13:32 Rui Wang <am...@apache.org> wrote:
>
> > Is the highlight section a right place for [1] as it has bigger impact?
> >
> >
> > [1]
> >
> > https://github.com/apache/calcite/commit/19edf52c76c6a1507721f5bd37f2a33497aa0c4c
> >
> > -Rui
> >
> > On Fri, Aug 7, 2020 at 9:48 PM Andrei Sereda <an...@sereda.cc> wrote:
> >
> > > Hello,
> > >
> > > Does anybody want to mention any highlights for 1.25 besides removal of
> > > deprecated methods  ?
> > >
> > > Currently it says:
> > > =======
> > > This release comes shortly after 1.24.0 (in just two weeks) and removes
> > > methods which were deprecated in the previous version.
> > > =======
> > >
> > > Thanks,
> > > Andrei.
> > >
> > > On Fri, Aug 7, 2020 at 11:12 AM Andrei Sereda <an...@sereda.cc> wrote:
> > >
> > > > Hello,
> > > >
> > > > I'm starting the release today. If there are some PRs which you would
> > > like
> > > > to be included in 1.25 please let me know ASAP.
> > > >
> > > > This should be a quick release mostly for CALCITE-4136
> > > >
> > > > Thanks,
> > > > Andrei.
> > > >
> > > > On Fri, Aug 7, 2020 at 4:33 AM Julian Hyde <jh...@apache.org> wrote:
> > > >
> > > >> Andrei,
> > > >>
> > > >> We agreed that this would be a quick release. Above I mentioned Aug
> > > >> 8th as a target, and it's Aug 7th already. Can you start moving the
> > > >> release process along, please.
> > > >>
> > > >> Julian
> > > >>
> > > >> On Fri, Jul 24, 2020 at 2:23 PM Andrei Sereda <an...@sereda.cc>
> > wrote:
> > > >> >
> > > >> > Julian,
> > > >> >
> > > >> > Yes this time I should have enough cycles for the release.
> > > >> >
> > > >> > Also, I think Danny did the heavy lifting with 1.22 since it wasn't
> > an
> > > >> easy
> > > >> > one.
> > > >> >
> > > >> > Andrei.
> > > >> >
> > > >> > On Fri, Jul 24, 2020, 16:16 Julian Hyde <jh...@gmail.com>
> > > wrote:
> > > >> >
> > > >> > > Andrei,
> > > >> > >
> > > >> > > That would be great. Last time I recall you had a crunch at
> > $dayjob
> > > >> that
> > > >> > > didn’t leave you with enough cycles to be release manager. I think
> > > >> this
> > > >> > > release should be timely, so if that is a concern this time
> > around,
> > > >> let us
> > > >> > > know.
> > > >> > >
> > > >> > > (Maybe the fact that this release is very time-boxed will make
> > that
> > > >> less
> > > >> > > of a risk. I really think we could get this done in by Aug 8 -
> > i.e.
> > > 2
> > > >> weeks
> > > >> > > - if we focus.)
> > > >> > >
> > > >> > > Julian
> > > >> > >
> > > >> > >
> > > >> > > > On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc>
> > > >> wrote:
> > > >> > > >
> > > >> > > > It should be me.
> > > >> > > >
> > > >> > > > I swapped the 1.22 release with Danny Chen who was supposed to
> > be
> > > >> release
> > > >> > > > manager for 1.25
> > > >> > > >
> > > >> > > > On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <
> > hyuan@apache.org>
> > > >> wrote:
> > > >> > > >
> > > >> > > >> Do we have release manager for v1.25.0?
> > > >> > > >>
> > > >> > > >>
> > > >> > > >> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com>
> > > >> wrote:
> > > >> > > >>> The release vote for 1.24 RC0 just passed [1], and it will be
> > > >> released
> > > >> > > >> shortly.
> > > >> > > >>>
> > > >> > > >>> We planned that release 1.24 is a transitional release, and
> > 1.25
> > > >> will
> > > >> > > >> follow soon afterwards. 1.24 deprecates some APIs that we
> > intend
> > > to
> > > >> > > remove
> > > >> > > >> in 1.25. We had to make the release so that people can see that
> > > >> the APIs
> > > >> > > >> are deprecated, and replace them with the new versions.
> > > >> > > >>>
> > > >> > > >>> During the release vote we ran into 4136 [2]. This is a real
> > > bug,
> > > >> > > caused
> > > >> > > >> in part by the API changes to deprecate APIs (and provide
> > > long-term
> > > >> > > >> replacements) and in part caused by 4079 [3], the real bug that
> > > we
> > > >> are
> > > >> > > >> trying to solve in 1.25.
> > > >> > > >>>
> > > >> > > >>> So, it is important that we release 1.25 soon, and that it
> > > solves
> > > >> all
> > > >> > > of
> > > >> > > >> these problems. I don’t know whether people will perceive 1.24
> > > as a
> > > >> > > release
> > > >> > > >> “lower than our usual quality” (even though there are good
> > > reasons
> > > >> for
> > > >> > > it)
> > > >> > > >> but 1.25 needs to be back to the usual quality.
> > > >> > > >>>
> > > >> > > >>> Julian
> > > >> > > >>>
> > > >> > > >>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
> > > >> > > >> https://issues.apache.org/jira/browse/CALCITE-4117>
> > > >> > > >>>
> > > >> > > >>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
> > > >> > > >> https://issues.apache.org/jira/browse/CALCITE-4136>
> > > >> > > >>>
> > > >> > > >>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
> > > >> > > >> https://issues.apache.org/jira/browse/CALCITE-4079>
> > > >> > > >>
> > > >> > >
> > > >> > >
> > > >>
> > > >
> > >
> >

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Andrei Sereda <an...@sereda.cc>.

I would say yes.

On Sat, Aug 8, 2020, 13:32 Rui Wang <am...@apache.org> wrote:

> Is the highlight section a right place for [1] as it has bigger impact?
>
>
> [1]
>
> https://github.com/apache/calcite/commit/19edf52c76c6a1507721f5bd37f2a33497aa0c4c
>
> -Rui
>
> On Fri, Aug 7, 2020 at 9:48 PM Andrei Sereda <an...@sereda.cc> wrote:
>
> > Hello,
> >
> > Does anybody want to mention any highlights for 1.25 besides removal of
> > deprecated methods  ?
> >
> > Currently it says:
> > =======
> > This release comes shortly after 1.24.0 (in just two weeks) and removes
> > methods which were deprecated in the previous version.
> > =======
> >
> > Thanks,
> > Andrei.
> >
> > On Fri, Aug 7, 2020 at 11:12 AM Andrei Sereda <an...@sereda.cc> wrote:
> >
> > > Hello,
> > >
> > > I'm starting the release today. If there are some PRs which you would
> > like
> > > to be included in 1.25 please let me know ASAP.
> > >
> > > This should be a quick release mostly for CALCITE-4136
> > >
> > > Thanks,
> > > Andrei.
> > >
> > > On Fri, Aug 7, 2020 at 4:33 AM Julian Hyde <jh...@apache.org> wrote:
> > >
> > >> Andrei,
> > >>
> > >> We agreed that this would be a quick release. Above I mentioned Aug
> > >> 8th as a target, and it's Aug 7th already. Can you start moving the
> > >> release process along, please.
> > >>
> > >> Julian
> > >>
> > >> On Fri, Jul 24, 2020 at 2:23 PM Andrei Sereda <an...@sereda.cc>
> wrote:
> > >> >
> > >> > Julian,
> > >> >
> > >> > Yes this time I should have enough cycles for the release.
> > >> >
> > >> > Also, I think Danny did the heavy lifting with 1.22 since it wasn't
> an
> > >> easy
> > >> > one.
> > >> >
> > >> > Andrei.
> > >> >
> > >> > On Fri, Jul 24, 2020, 16:16 Julian Hyde <jh...@gmail.com>
> > wrote:
> > >> >
> > >> > > Andrei,
> > >> > >
> > >> > > That would be great. Last time I recall you had a crunch at
> $dayjob
> > >> that
> > >> > > didn’t leave you with enough cycles to be release manager. I think
> > >> this
> > >> > > release should be timely, so if that is a concern this time
> around,
> > >> let us
> > >> > > know.
> > >> > >
> > >> > > (Maybe the fact that this release is very time-boxed will make
> that
> > >> less
> > >> > > of a risk. I really think we could get this done in by Aug 8 -
> i.e.
> > 2
> > >> weeks
> > >> > > - if we focus.)
> > >> > >
> > >> > > Julian
> > >> > >
> > >> > >
> > >> > > > On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc>
> > >> wrote:
> > >> > > >
> > >> > > > It should be me.
> > >> > > >
> > >> > > > I swapped the 1.22 release with Danny Chen who was supposed to
> be
> > >> release
> > >> > > > manager for 1.25
> > >> > > >
> > >> > > > On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <
> hyuan@apache.org>
> > >> wrote:
> > >> > > >
> > >> > > >> Do we have release manager for v1.25.0?
> > >> > > >>
> > >> > > >>
> > >> > > >> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com>
> > >> wrote:
> > >> > > >>> The release vote for 1.24 RC0 just passed [1], and it will be
> > >> released
> > >> > > >> shortly.
> > >> > > >>>
> > >> > > >>> We planned that release 1.24 is a transitional release, and
> 1.25
> > >> will
> > >> > > >> follow soon afterwards. 1.24 deprecates some APIs that we
> intend
> > to
> > >> > > remove
> > >> > > >> in 1.25. We had to make the release so that people can see that
> > >> the APIs
> > >> > > >> are deprecated, and replace them with the new versions.
> > >> > > >>>
> > >> > > >>> During the release vote we ran into 4136 [2]. This is a real
> > bug,
> > >> > > caused
> > >> > > >> in part by the API changes to deprecate APIs (and provide
> > long-term
> > >> > > >> replacements) and in part caused by 4079 [3], the real bug that
> > we
> > >> are
> > >> > > >> trying to solve in 1.25.
> > >> > > >>>
> > >> > > >>> So, it is important that we release 1.25 soon, and that it
> > solves
> > >> all
> > >> > > of
> > >> > > >> these problems. I don’t know whether people will perceive 1.24
> > as a
> > >> > > release
> > >> > > >> “lower than our usual quality” (even though there are good
> > reasons
> > >> for
> > >> > > it)
> > >> > > >> but 1.25 needs to be back to the usual quality.
> > >> > > >>>
> > >> > > >>> Julian
> > >> > > >>>
> > >> > > >>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
> > >> > > >> https://issues.apache.org/jira/browse/CALCITE-4117>
> > >> > > >>>
> > >> > > >>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
> > >> > > >> https://issues.apache.org/jira/browse/CALCITE-4136>
> > >> > > >>>
> > >> > > >>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
> > >> > > >> https://issues.apache.org/jira/browse/CALCITE-4079>
> > >> > > >>
> > >> > >
> > >> > >
> > >>
> > >
> >
>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Rui Wang <am...@apache.org>.

Is the highlight section a right place for [1] as it has bigger impact?


[1]
https://github.com/apache/calcite/commit/19edf52c76c6a1507721f5bd37f2a33497aa0c4c

-Rui

On Fri, Aug 7, 2020 at 9:48 PM Andrei Sereda <an...@sereda.cc> wrote:

> Hello,
>
> Does anybody want to mention any highlights for 1.25 besides removal of
> deprecated methods  ?
>
> Currently it says:
> =======
> This release comes shortly after 1.24.0 (in just two weeks) and removes
> methods which were deprecated in the previous version.
> =======
>
> Thanks,
> Andrei.
>
> On Fri, Aug 7, 2020 at 11:12 AM Andrei Sereda <an...@sereda.cc> wrote:
>
> > Hello,
> >
> > I'm starting the release today. If there are some PRs which you would
> like
> > to be included in 1.25 please let me know ASAP.
> >
> > This should be a quick release mostly for CALCITE-4136
> >
> > Thanks,
> > Andrei.
> >
> > On Fri, Aug 7, 2020 at 4:33 AM Julian Hyde <jh...@apache.org> wrote:
> >
> >> Andrei,
> >>
> >> We agreed that this would be a quick release. Above I mentioned Aug
> >> 8th as a target, and it's Aug 7th already. Can you start moving the
> >> release process along, please.
> >>
> >> Julian
> >>
> >> On Fri, Jul 24, 2020 at 2:23 PM Andrei Sereda <an...@sereda.cc> wrote:
> >> >
> >> > Julian,
> >> >
> >> > Yes this time I should have enough cycles for the release.
> >> >
> >> > Also, I think Danny did the heavy lifting with 1.22 since it wasn't an
> >> easy
> >> > one.
> >> >
> >> > Andrei.
> >> >
> >> > On Fri, Jul 24, 2020, 16:16 Julian Hyde <jh...@gmail.com>
> wrote:
> >> >
> >> > > Andrei,
> >> > >
> >> > > That would be great. Last time I recall you had a crunch at $dayjob
> >> that
> >> > > didn’t leave you with enough cycles to be release manager. I think
> >> this
> >> > > release should be timely, so if that is a concern this time around,
> >> let us
> >> > > know.
> >> > >
> >> > > (Maybe the fact that this release is very time-boxed will make that
> >> less
> >> > > of a risk. I really think we could get this done in by Aug 8 - i.e.
> 2
> >> weeks
> >> > > - if we focus.)
> >> > >
> >> > > Julian
> >> > >
> >> > >
> >> > > > On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc>
> >> wrote:
> >> > > >
> >> > > > It should be me.
> >> > > >
> >> > > > I swapped the 1.22 release with Danny Chen who was supposed to be
> >> release
> >> > > > manager for 1.25
> >> > > >
> >> > > > On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <hy...@apache.org>
> >> wrote:
> >> > > >
> >> > > >> Do we have release manager for v1.25.0?
> >> > > >>
> >> > > >>
> >> > > >> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com>
> >> wrote:
> >> > > >>> The release vote for 1.24 RC0 just passed [1], and it will be
> >> released
> >> > > >> shortly.
> >> > > >>>
> >> > > >>> We planned that release 1.24 is a transitional release, and 1.25
> >> will
> >> > > >> follow soon afterwards. 1.24 deprecates some APIs that we intend
> to
> >> > > remove
> >> > > >> in 1.25. We had to make the release so that people can see that
> >> the APIs
> >> > > >> are deprecated, and replace them with the new versions.
> >> > > >>>
> >> > > >>> During the release vote we ran into 4136 [2]. This is a real
> bug,
> >> > > caused
> >> > > >> in part by the API changes to deprecate APIs (and provide
> long-term
> >> > > >> replacements) and in part caused by 4079 [3], the real bug that
> we
> >> are
> >> > > >> trying to solve in 1.25.
> >> > > >>>
> >> > > >>> So, it is important that we release 1.25 soon, and that it
> solves
> >> all
> >> > > of
> >> > > >> these problems. I don’t know whether people will perceive 1.24
> as a
> >> > > release
> >> > > >> “lower than our usual quality” (even though there are good
> reasons
> >> for
> >> > > it)
> >> > > >> but 1.25 needs to be back to the usual quality.
> >> > > >>>
> >> > > >>> Julian
> >> > > >>>
> >> > > >>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
> >> > > >> https://issues.apache.org/jira/browse/CALCITE-4117>
> >> > > >>>
> >> > > >>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
> >> > > >> https://issues.apache.org/jira/browse/CALCITE-4136>
> >> > > >>>
> >> > > >>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
> >> > > >> https://issues.apache.org/jira/browse/CALCITE-4079>
> >> > > >>
> >> > >
> >> > >
> >>
> >
>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Andrei Sereda <an...@sereda.cc>.

Hello,

Does anybody want to mention any highlights for 1.25 besides removal of
deprecated methods  ?

Currently it says:
=======
This release comes shortly after 1.24.0 (in just two weeks) and removes
methods which were deprecated in the previous version.
=======

Thanks,
Andrei.

On Fri, Aug 7, 2020 at 11:12 AM Andrei Sereda <an...@sereda.cc> wrote:

> Hello,
>
> I'm starting the release today. If there are some PRs which you would like
> to be included in 1.25 please let me know ASAP.
>
> This should be a quick release mostly for CALCITE-4136
>
> Thanks,
> Andrei.
>
> On Fri, Aug 7, 2020 at 4:33 AM Julian Hyde <jh...@apache.org> wrote:
>
>> Andrei,
>>
>> We agreed that this would be a quick release. Above I mentioned Aug
>> 8th as a target, and it's Aug 7th already. Can you start moving the
>> release process along, please.
>>
>> Julian
>>
>> On Fri, Jul 24, 2020 at 2:23 PM Andrei Sereda <an...@sereda.cc> wrote:
>> >
>> > Julian,
>> >
>> > Yes this time I should have enough cycles for the release.
>> >
>> > Also, I think Danny did the heavy lifting with 1.22 since it wasn't an
>> easy
>> > one.
>> >
>> > Andrei.
>> >
>> > On Fri, Jul 24, 2020, 16:16 Julian Hyde <jh...@gmail.com> wrote:
>> >
>> > > Andrei,
>> > >
>> > > That would be great. Last time I recall you had a crunch at $dayjob
>> that
>> > > didn’t leave you with enough cycles to be release manager. I think
>> this
>> > > release should be timely, so if that is a concern this time around,
>> let us
>> > > know.
>> > >
>> > > (Maybe the fact that this release is very time-boxed will make that
>> less
>> > > of a risk. I really think we could get this done in by Aug 8 - i.e. 2
>> weeks
>> > > - if we focus.)
>> > >
>> > > Julian
>> > >
>> > >
>> > > > On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc>
>> wrote:
>> > > >
>> > > > It should be me.
>> > > >
>> > > > I swapped the 1.22 release with Danny Chen who was supposed to be
>> release
>> > > > manager for 1.25
>> > > >
>> > > > On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <hy...@apache.org>
>> wrote:
>> > > >
>> > > >> Do we have release manager for v1.25.0?
>> > > >>
>> > > >>
>> > > >> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com>
>> wrote:
>> > > >>> The release vote for 1.24 RC0 just passed [1], and it will be
>> released
>> > > >> shortly.
>> > > >>>
>> > > >>> We planned that release 1.24 is a transitional release, and 1.25
>> will
>> > > >> follow soon afterwards. 1.24 deprecates some APIs that we intend to
>> > > remove
>> > > >> in 1.25. We had to make the release so that people can see that
>> the APIs
>> > > >> are deprecated, and replace them with the new versions.
>> > > >>>
>> > > >>> During the release vote we ran into 4136 [2]. This is a real bug,
>> > > caused
>> > > >> in part by the API changes to deprecate APIs (and provide long-term
>> > > >> replacements) and in part caused by 4079 [3], the real bug that we
>> are
>> > > >> trying to solve in 1.25.
>> > > >>>
>> > > >>> So, it is important that we release 1.25 soon, and that it solves
>> all
>> > > of
>> > > >> these problems. I don’t know whether people will perceive 1.24 as a
>> > > release
>> > > >> “lower than our usual quality” (even though there are good reasons
>> for
>> > > it)
>> > > >> but 1.25 needs to be back to the usual quality.
>> > > >>>
>> > > >>> Julian
>> > > >>>
>> > > >>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
>> > > >> https://issues.apache.org/jira/browse/CALCITE-4117>
>> > > >>>
>> > > >>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
>> > > >> https://issues.apache.org/jira/browse/CALCITE-4136>
>> > > >>>
>> > > >>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
>> > > >> https://issues.apache.org/jira/browse/CALCITE-4079>
>> > > >>
>> > >
>> > >
>>
>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Andrei Sereda <an...@sereda.cc>.

Hello,

I'm starting the release today. If there are some PRs which you would like
to be included in 1.25 please let me know ASAP.

This should be a quick release mostly for CALCITE-4136

Thanks,
Andrei.

On Fri, Aug 7, 2020 at 4:33 AM Julian Hyde <jh...@apache.org> wrote:

> Andrei,
>
> We agreed that this would be a quick release. Above I mentioned Aug
> 8th as a target, and it's Aug 7th already. Can you start moving the
> release process along, please.
>
> Julian
>
> On Fri, Jul 24, 2020 at 2:23 PM Andrei Sereda <an...@sereda.cc> wrote:
> >
> > Julian,
> >
> > Yes this time I should have enough cycles for the release.
> >
> > Also, I think Danny did the heavy lifting with 1.22 since it wasn't an
> easy
> > one.
> >
> > Andrei.
> >
> > On Fri, Jul 24, 2020, 16:16 Julian Hyde <jh...@gmail.com> wrote:
> >
> > > Andrei,
> > >
> > > That would be great. Last time I recall you had a crunch at $dayjob
> that
> > > didn’t leave you with enough cycles to be release manager. I think this
> > > release should be timely, so if that is a concern this time around,
> let us
> > > know.
> > >
> > > (Maybe the fact that this release is very time-boxed will make that
> less
> > > of a risk. I really think we could get this done in by Aug 8 - i.e. 2
> weeks
> > > - if we focus.)
> > >
> > > Julian
> > >
> > >
> > > > On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc> wrote:
> > > >
> > > > It should be me.
> > > >
> > > > I swapped the 1.22 release with Danny Chen who was supposed to be
> release
> > > > manager for 1.25
> > > >
> > > > On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <hy...@apache.org>
> wrote:
> > > >
> > > >> Do we have release manager for v1.25.0?
> > > >>
> > > >>
> > > >> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com> wrote:
> > > >>> The release vote for 1.24 RC0 just passed [1], and it will be
> released
> > > >> shortly.
> > > >>>
> > > >>> We planned that release 1.24 is a transitional release, and 1.25
> will
> > > >> follow soon afterwards. 1.24 deprecates some APIs that we intend to
> > > remove
> > > >> in 1.25. We had to make the release so that people can see that the
> APIs
> > > >> are deprecated, and replace them with the new versions.
> > > >>>
> > > >>> During the release vote we ran into 4136 [2]. This is a real bug,
> > > caused
> > > >> in part by the API changes to deprecate APIs (and provide long-term
> > > >> replacements) and in part caused by 4079 [3], the real bug that we
> are
> > > >> trying to solve in 1.25.
> > > >>>
> > > >>> So, it is important that we release 1.25 soon, and that it solves
> all
> > > of
> > > >> these problems. I don’t know whether people will perceive 1.24 as a
> > > release
> > > >> “lower than our usual quality” (even though there are good reasons
> for
> > > it)
> > > >> but 1.25 needs to be back to the usual quality.
> > > >>>
> > > >>> Julian
> > > >>>
> > > >>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
> > > >> https://issues.apache.org/jira/browse/CALCITE-4117>
> > > >>>
> > > >>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
> > > >> https://issues.apache.org/jira/browse/CALCITE-4136>
> > > >>>
> > > >>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
> > > >> https://issues.apache.org/jira/browse/CALCITE-4079>
> > > >>
> > >
> > >
>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Julian Hyde <jh...@apache.org>.

Andrei,

We agreed that this would be a quick release. Above I mentioned Aug
8th as a target, and it's Aug 7th already. Can you start moving the
release process along, please.

Julian

On Fri, Jul 24, 2020 at 2:23 PM Andrei Sereda <an...@sereda.cc> wrote:
>
> Julian,
>
> Yes this time I should have enough cycles for the release.
>
> Also, I think Danny did the heavy lifting with 1.22 since it wasn't an easy
> one.
>
> Andrei.
>
> On Fri, Jul 24, 2020, 16:16 Julian Hyde <jh...@gmail.com> wrote:
>
> > Andrei,
> >
> > That would be great. Last time I recall you had a crunch at $dayjob that
> > didn’t leave you with enough cycles to be release manager. I think this
> > release should be timely, so if that is a concern this time around, let us
> > know.
> >
> > (Maybe the fact that this release is very time-boxed will make that less
> > of a risk. I really think we could get this done in by Aug 8 - i.e. 2 weeks
> > - if we focus.)
> >
> > Julian
> >
> >
> > > On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc> wrote:
> > >
> > > It should be me.
> > >
> > > I swapped the 1.22 release with Danny Chen who was supposed to be release
> > > manager for 1.25
> > >
> > > On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <hy...@apache.org> wrote:
> > >
> > >> Do we have release manager for v1.25.0?
> > >>
> > >>
> > >> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com> wrote:
> > >>> The release vote for 1.24 RC0 just passed [1], and it will be released
> > >> shortly.
> > >>>
> > >>> We planned that release 1.24 is a transitional release, and 1.25 will
> > >> follow soon afterwards. 1.24 deprecates some APIs that we intend to
> > remove
> > >> in 1.25. We had to make the release so that people can see that the APIs
> > >> are deprecated, and replace them with the new versions.
> > >>>
> > >>> During the release vote we ran into 4136 [2]. This is a real bug,
> > caused
> > >> in part by the API changes to deprecate APIs (and provide long-term
> > >> replacements) and in part caused by 4079 [3], the real bug that we are
> > >> trying to solve in 1.25.
> > >>>
> > >>> So, it is important that we release 1.25 soon, and that it solves all
> > of
> > >> these problems. I don’t know whether people will perceive 1.24 as a
> > release
> > >> “lower than our usual quality” (even though there are good reasons for
> > it)
> > >> but 1.25 needs to be back to the usual quality.
> > >>>
> > >>> Julian
> > >>>
> > >>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
> > >> https://issues.apache.org/jira/browse/CALCITE-4117>
> > >>>
> > >>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
> > >> https://issues.apache.org/jira/browse/CALCITE-4136>
> > >>>
> > >>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
> > >> https://issues.apache.org/jira/browse/CALCITE-4079>
> > >>
> >
> >

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Andrei Sereda <an...@sereda.cc>.

Julian,

Yes this time I should have enough cycles for the release.

Also, I think Danny did the heavy lifting with 1.22 since it wasn't an easy
one.

Andrei.

On Fri, Jul 24, 2020, 16:16 Julian Hyde <jh...@gmail.com> wrote:

> Andrei,
>
> That would be great. Last time I recall you had a crunch at $dayjob that
> didn’t leave you with enough cycles to be release manager. I think this
> release should be timely, so if that is a concern this time around, let us
> know.
>
> (Maybe the fact that this release is very time-boxed will make that less
> of a risk. I really think we could get this done in by Aug 8 - i.e. 2 weeks
> - if we focus.)
>
> Julian
>
>
> > On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc> wrote:
> >
> > It should be me.
> >
> > I swapped the 1.22 release with Danny Chen who was supposed to be release
> > manager for 1.25
> >
> > On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <hy...@apache.org> wrote:
> >
> >> Do we have release manager for v1.25.0?
> >>
> >>
> >> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com> wrote:
> >>> The release vote for 1.24 RC0 just passed [1], and it will be released
> >> shortly.
> >>>
> >>> We planned that release 1.24 is a transitional release, and 1.25 will
> >> follow soon afterwards. 1.24 deprecates some APIs that we intend to
> remove
> >> in 1.25. We had to make the release so that people can see that the APIs
> >> are deprecated, and replace them with the new versions.
> >>>
> >>> During the release vote we ran into 4136 [2]. This is a real bug,
> caused
> >> in part by the API changes to deprecate APIs (and provide long-term
> >> replacements) and in part caused by 4079 [3], the real bug that we are
> >> trying to solve in 1.25.
> >>>
> >>> So, it is important that we release 1.25 soon, and that it solves all
> of
> >> these problems. I don’t know whether people will perceive 1.24 as a
> release
> >> “lower than our usual quality” (even though there are good reasons for
> it)
> >> but 1.25 needs to be back to the usual quality.
> >>>
> >>> Julian
> >>>
> >>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
> >> https://issues.apache.org/jira/browse/CALCITE-4117>
> >>>
> >>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
> >> https://issues.apache.org/jira/browse/CALCITE-4136>
> >>>
> >>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
> >> https://issues.apache.org/jira/browse/CALCITE-4079>
> >>
>
>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Julian Hyde <jh...@gmail.com>.

Andrei,

That would be great. Last time I recall you had a crunch at $dayjob that didn’t leave you with enough cycles to be release manager. I think this release should be timely, so if that is a concern this time around, let us know.

(Maybe the fact that this release is very time-boxed will make that less of a risk. I really think we could get this done in by Aug 8 - i.e. 2 weeks - if we focus.)

Julian


> On Jul 24, 2020, at 9:57 AM, Andrei Sereda <an...@sereda.cc> wrote:
> 
> It should be me.
> 
> I swapped the 1.22 release with Danny Chen who was supposed to be release
> manager for 1.25
> 
> On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <hy...@apache.org> wrote:
> 
>> Do we have release manager for v1.25.0?
>> 
>> 
>> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com> wrote:
>>> The release vote for 1.24 RC0 just passed [1], and it will be released
>> shortly.
>>> 
>>> We planned that release 1.24 is a transitional release, and 1.25 will
>> follow soon afterwards. 1.24 deprecates some APIs that we intend to remove
>> in 1.25. We had to make the release so that people can see that the APIs
>> are deprecated, and replace them with the new versions.
>>> 
>>> During the release vote we ran into 4136 [2]. This is a real bug, caused
>> in part by the API changes to deprecate APIs (and provide long-term
>> replacements) and in part caused by 4079 [3], the real bug that we are
>> trying to solve in 1.25.
>>> 
>>> So, it is important that we release 1.25 soon, and that it solves all of
>> these problems. I don’t know whether people will perceive 1.24 as a release
>> “lower than our usual quality” (even though there are good reasons for it)
>> but 1.25 needs to be back to the usual quality.
>>> 
>>> Julian
>>> 
>>> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
>> https://issues.apache.org/jira/browse/CALCITE-4117>
>>> 
>>> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
>> https://issues.apache.org/jira/browse/CALCITE-4136>
>>> 
>>> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
>> https://issues.apache.org/jira/browse/CALCITE-4079>
>>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Andrei Sereda <an...@sereda.cc>.

It should be me.

I swapped the 1.22 release with Danny Chen who was supposed to be release
manager for 1.25

On Fri, Jul 24, 2020 at 12:52 PM Haisheng Yuan <hy...@apache.org> wrote:

> Do we have release manager for v1.25.0?
>
>
> On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com> wrote:
> > The release vote for 1.24 RC0 just passed [1], and it will be released
> shortly.
> >
> > We planned that release 1.24 is a transitional release, and 1.25 will
> follow soon afterwards. 1.24 deprecates some APIs that we intend to remove
> in 1.25. We had to make the release so that people can see that the APIs
> are deprecated, and replace them with the new versions.
> >
> > During the release vote we ran into 4136 [2]. This is a real bug, caused
> in part by the API changes to deprecate APIs (and provide long-term
> replacements) and in part caused by 4079 [3], the real bug that we are
> trying to solve in 1.25.
> >
> > So, it is important that we release 1.25 soon, and that it solves all of
> these problems. I don’t know whether people will perceive 1.24 as a release
> “lower than our usual quality” (even though there are good reasons for it)
> but 1.25 needs to be back to the usual quality.
> >
> > Julian
> >
> > [1] https://issues.apache.org/jira/browse/CALCITE-4117 <
> https://issues.apache.org/jira/browse/CALCITE-4117>
> >
> > [2] https://issues.apache.org/jira/browse/CALCITE-4136 <
> https://issues.apache.org/jira/browse/CALCITE-4136>
> >
> > [3] https://issues.apache.org/jira/browse/CALCITE-4079 <
> https://issues.apache.org/jira/browse/CALCITE-4079>
>

Re: [DISCUSS] Towards Calcite 1.25.0

Posted by Haisheng Yuan <hy...@apache.org>.

Do we have release manager for v1.25.0?


On 2020/07/23 17:15:12, Julian Hyde <jh...@gmail.com> wrote: 
> The release vote for 1.24 RC0 just passed [1], and it will be released shortly.
> 
> We planned that release 1.24 is a transitional release, and 1.25 will follow soon afterwards. 1.24 deprecates some APIs that we intend to remove in 1.25. We had to make the release so that people can see that the APIs are deprecated, and replace them with the new versions.
> 
> During the release vote we ran into 4136 [2]. This is a real bug, caused in part by the API changes to deprecate APIs (and provide long-term replacements) and in part caused by 4079 [3], the real bug that we are trying to solve in 1.25.
> 
> So, it is important that we release 1.25 soon, and that it solves all of these problems. I don’t know whether people will perceive 1.24 as a release “lower than our usual quality” (even though there are good reasons for it) but 1.25 needs to be back to the usual quality.
> 
> Julian
> 
> [1] https://issues.apache.org/jira/browse/CALCITE-4117 <https://issues.apache.org/jira/browse/CALCITE-4117>
> 
> [2] https://issues.apache.org/jira/browse/CALCITE-4136 <https://issues.apache.org/jira/browse/CALCITE-4136>
> 
> [3] https://issues.apache.org/jira/browse/CALCITE-4079 <https://issues.apache.org/jira/browse/CALCITE-4079>