I started building the first release candidate. The main branch is now frozen until further updates.
Best, Stamatis On Mon, May 25, 2026 at 5:40 AM Yu Xu <[email protected]> wrote: > > I don't want this Jira (https://issues.apache.org/jira/browse/CALCITE-5406) > issue to delay the 1.42 release, so I removed the fixed version. > > On 2026/05/24 07:13:15 Stamatis Zampetakis wrote: > > Hi team, > > > > Thanks to everyone's help, only a handful of tickets are pending for > > the 1.42.0 release [1]. I am planning to cut the first release > > candidate on May 27 and hopefully by then all the necessary issues > > will be resolved. > > > > You can find the tentative release notes in [2]. Feel free to review > > them and leave your comments. I will update the PR accordingly with > > the last few issues that will be resolved between now and Wednesday. > > > > I encourage everyone to start testing version 1.42.0 in downstream > > projects so that we avoid going through multiple RC votes. > > > > Best, > > Stamatis > > > > [1] > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > [2] https://github.com/apache/calcite/pull/4964 > > > > On Mon, May 18, 2026 at 8:18 AM Yu Xu <[email protected]> wrote: > > > > > > Thanks Stamatis for the 1.42.0 release! Regarding support for the > > > DISTINCT ON syntax, there is currently one completed PR and initial > > > review. I've temporarily changed the version information to 1.42, hoping > > > someone in the community will assist with the final review. If the > > > timeframe feels too rushed, it can be changed to 1.43. Based on previous > > > discussions, I've outlined the benefits of introducing this syntax. > > > > > > Related Jira: https://issues.apache.org/jira/browse/CALCITE-5406 > > > > > > On 2026/04/28 06:30:12 Stamatis Zampetakis wrote: > > > > Hey everyone, > > > > > > > > I was planning to take on the Calcite 1.43.0 release but given that we > > > > have no volunteers for 1.42.0 I can switch to that one. > > > > Regarding timing, I can cut the first release candidate sometime > > > > during the week of May 18. > > > > This allows a little over 2 weeks for finalizing and merging pending > > > > PRs to main. > > > > > > > > We currently have over 200 unreleased commits in main so if we don't > > > > have any significant blockers or regressions, I would suggest > > > > not to push the release cut too much in the future. I see a few > > > > pending issues in the release dashboard [1] but nothing is very > > > > urgent. > > > > Please set the Fix Version accordingly for anything that must be in > > > > the next release. > > > > > > > > Although not mandatory, releasing Avatica before then would be > > > > beneficial since it has been a while since the last release. > > > > > > > > Best, > > > > Stamatis > > > > > > > > [1] > > > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950 > > > > > > > > On Mon, Apr 27, 2026 at 1:19 PM ткаленко кирилл <[email protected]> > > > > wrote: > > > > > > > > > > Any news? > > > > > >
