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 <jhyde.apa...@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> >
