+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
