Thanks Benchao for driving the discussion. I would like to be release manager for 1.39.0 version. Besides, I could help to review some open pull requests.
-- Best, Jing Zhang James Duong <james.du...@improving.com.invalid> 于2024年3月19日周二 01:14写道： > I’ll help take a look at some of the open Avatica and Calcite PRs. > > From: Mihai Budiu <mbu...@gmail.com> > Date: Monday, March 18, 2024 at 9:48 AM > To: dev@calcite.apache.org <dev@calcite.apache.org> > Subject: Re: [DISCUSS] Towards Calcite 1.37.0 > This would be great, I am fixing two very basic bugs. > Was busy with some other stuff, so I didn't have time to figure out how to > submit the PRs so that they pass, if anyone has more detailed instructions > I would be very happy. Otherwise I will dig into it. > > Mihai > ________________________________ > From: Francis Chuang <francischu...@apache.org> > Sent: Sunday, March 17, 2024 2:44 PM > To: dev@calcite.apache.org <dev@calcite.apache.org> > Subject: Re: [DISCUSS] Towards Calcite 1.37.0 > > Hey everyone, > > I just wanted to jump in regarding CALCITE-6248 [1] and CALCITE-6282 (no > corresponding PRs in the Calcite repo yet). > > The corresponding PRs in the Avatica repo are: > - https://github.com/apache/calcite-avatica/pull/238 > - https://github.com/apache/calcite-avatica/pull/241 > > As the issue will require changes to both Calcite and Avatica in a > coordinated fashion, what do you guys think about releasing Avatica > 1.25.0 first? I can be RM for the Avatica release. > > Mihai, can you please confirm if this approach works for you? > > Discussion for getting changes simultaneously into both Avatica and > Calcite is here [2]. > > Francis > > [1] https://github.com/apache/calcite/pull/3708 > [2] https://lists.apache.org/thread/5w3ry3zbm7671ffp4pxh7lx6cgc5r3tq > > On 13/03/2024 10:07 pm, Benchao Li wrote: > > Thank you, Hongyu, for volunteering to be a release manager. > > > > What's worth to mention is that to be a release manager does not > > require PMC membership nor being a committer, and it is a good chance > > to be involved in community activities apart from code/discussion, > > which would be a good additional credit for being considered as > > committer or PMC member candidate. > > > > Hongyu Guo <guohongyu...@gmail.com> 于2024年3月13日周三 11:29写道： > >> > >> I would like to take on the role of RM for one release > >> > >> On Thu, Mar 7, 2024 at 2:58 AM Alessandro Solimando < > >> alessandro.solima...@gmail.com> wrote: > >> > >>> Hey Sergey, > >>> thanks for being the release manager for 1.37.0. > >>> > >>> I have added fixVersion=1.37.0 to CALCITE-2040 > >>> <https://issues.apache.org/jira/browse/CALCITE-2040>, as its > associated PR > >>> <https://github.com/apache/calcite/pull/3666> is in good shape IMO, > and we > >>> are trying to get it done shortly with Hongyu. > >>> > >>> Best regards, > >>> Alessandro > >>> > >>> On Wed, 6 Mar 2024 at 16:49, Sergey Nuyanzin <snuyan...@gmail.com> > wrote: > >>> > >>>> Updates about 1.37.0 releasing > >>>> > >>>> According to our Jira dashboard [1] and Github [2], there > >>>> are 17 pending issues that could / should be part of the release. > >>>> I'd propose to make a collective effort to try to clean up our 1.37.0 > >>>> backlog and merge the PRs which are in a good state. I'd propose to > >>>> aim for about 2 weeks to release 1.37.0, this will give us about > >>>> some time to clean up pending PRs for the next version. What do you > >>> think? > >>>> > >>>> And contributors, if you have any work that is in good shape and want > >>>> to be included in 1.37.0, please mark the fixVersion to 1.37.0, this > >>>> will inform the release manager, and we'll try our best to get it in. > >>>> > >>>> A quick update on the current status for issues targeted 1.37.0 > >>>> We need more reviewers for #2 > >>>> > >>>> #1. Issues already have reviewers, and seems promising to be merged > >>> shortly > >>>> https://issues.apache.org/jira/browse/CALCITE-6138 > >>>> https://issues.apache.org/jira/browse/CALCITE-6015 > >>>> https://issues.apache.org/jira/browse/CALCITE-6283 > >>>> https://issues.apache.org/jira/browse/CALCITE-5607 > >>>> > >>>> #2. Issues has been reviewed, and needs another reviewer > >>>> https://issues.apache.org/jira/browse/CALCITE-3522 > >>>> https://issues.apache.org/jira/browse/CALCITE-6071 > >>>> https://issues.apache.org/jira/browse/CALCITE-6210 > >>>> https://issues.apache.org/jira/browse/CALCITE-6259 > >>>> https://issues.apache.org/jira/browse/CALCITE-2067 > >>>> https://issues.apache.org/jira/browse/CALCITE-6226 > >>>> https://issues.apache.org/jira/browse/CALCITE-6193 > >>>> > >>>> > >>>> It could happen that I miss something, please let me know > >>>> if there is something with fixVersion 1.37.0 ready for review and not > >>>> mentioned here > >>>> > >>>> Also I created a JIRA issue for releasing 1.37.0 > >>>> https://issues.apache.org/jira/browse/CALCITE-6302 > >>>> > >>>> [1] > >>>> > >>> > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > >>>> [2] https://github.com/apache/calcite/pulls > >>>> > >>>> On Fri, Feb 23, 2024 at 9:24 PM Julian Hyde <jhyde.apa...@gmail.com> > >>>> wrote: > >>>> > >>>>> +1 for a release. > >>>>> > >>>>> Our users rely on a regular cadence of releases. If someone submits a > >>>>> patch and doesn’t see it in a release until 6 months later (or it > sits > >>>>> un-reviewed) they will be less inclined to submit a patch. > >>>>> > >>>>> Yeah, I know Open Source Doesn’t Require Providing Builds [1] but it > >>>> makes > >>>>> everyone’s life easier. > >>>>> > >>>>> Julian > >>>>> > >>>>> [1] https://news.ycombinator.com/item?id=39094387 > >>>>> > >>>>> > >>>>>> On Feb 21, 2024, at 1:18 AM, Stamatis Zampetakis <zabe...@gmail.com > > > >>>>> wrote: > >>>>>> > >>>>>> With so many commits it's definitely a good time to cut a new > >>> release. > >>>>>> > >>>>>> I can be the RM for 1.39.0 or 1.40.0 depending on the timing. > >>>>>> > >>>>>> Best, > >>>>>> Stamatis > >>>>>> > >>>>>> On Wed, Feb 21, 2024 at 12:10 AM Sergey Nuyanzin < > >>> snuyan...@gmail.com> > >>>>> wrote: > >>>>>>> > >>>>>>> Thanks for starting the discussion > >>>>>>> > >>>>>>>> @Sergey, are you still available for being the release manager for > >>>>> 1.37.0? > >>>>>>> > >>>>>>> I think so, in theory I could start with some steps in one/two > weeks > >>>> if > >>>>>>> there is no objections > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> On Mon, Feb 19, 2024 at 12:29 PM Benchao Li <libenc...@apache.org> > >>>>> wrote: > >>>>>>> > >>>>>>>> It's been a bit more than 3 months since our last release > >>>> (2023-11-10) > >>>>>>>> [1] and there are currently 100+ new commits in main branch. Per > >>> our > >>>>>>>> tradition of producing one release every 2-3 months, I think it's > >>>> time > >>>>>>>> to consider for next release now. > >>>>>>>> > >>>>>>>> According to [2], the following release managers would be: > >>>>>>>> - 1.37.0 Sergey Nuyanzin > >>>>>>>> - 1.38.0 Julian Hyde > >>>>>>>> > >>>>>>>> @Sergey, are you still available for being the release manager for > >>>>> 1.37.0? > >>>>>>>> > >>>>>>>> Besides, we need more volunteers for the next releases (version >= > >>>>>>>> 1.39.0), anyone who is interested in doing it can reply in this > >>>>>>>> thread. > >>>>>>>> > >>>>>>>> [1] https://calcite.apache.org/docs/history.html#v1-36-0 > >>>>>>>> [4] > >>> https://lists.apache.org/thread/tm3t42qvpq3db24xtd2g468ofv83l6hk > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> > >>>>>>>> Best, > >>>>>>>> Benchao Li > >>>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> Best regards, > >>>>>>> Sergey > >>>>> > >>>>> > >>>> > >>>> -- > >>>> Best regards, > >>>> Sergey > >>>> > >>> > > > > > > > Warning: The sender of this message could not be validated and may not be > the actual sender. >
