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
