[jira] [Created] (CALCITE-6335) Quidem tests should allow specifying optimization passes to apply to programs

[Mihai Budiu (Jira)]

Mihai Budiu created CALCITE-6335:


 Summary: Quidem tests should allow specifying optimization passes 
to apply to programs
 Key: CALCITE-6335
 URL: https://issues.apache.org/jira/browse/CALCITE-6335
 Project: Calcite
  Issue Type: Improvement
  Components: core
Affects Versions: 1.36.0
Reporter: Mihai Budiu


This facility would make it much easier to test various optimization passes.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: Using quidem tests to validate optimization rules

[Julian Hyde]

You are correct. There is no mechanism, and one would be really useful.

> On Mar 18, 2024, at 1:19 PM, Mihai Budiu  wrote:
> 
> Hello,
> 
> I was looking around to see whether it's possible to use a quidem test to 
> exercise specific optimization rules, but I couldn't find anything. Is there 
> such a mechanism, or should I file an issue to create one?
> 
> Thank you,
> Mihai

Using quidem tests to validate optimization rules

[Mihai Budiu]

Hello,

I was looking around to see whether it's possible to use a quidem test to 
exercise specific optimization rules, but I couldn't find anything. Is there 
such a mechanism, or should I file an issue to create one?

Thank you,
Mihai

Re: [DISCUSS] Towards Calcite 1.37.0

[James Duong]

I’ll help take a look at some of the open Avatica and Calcite PRs.

From: Mihai Budiu 
Date: Monday, March 18, 2024 at 9:48 AM
To: 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 
Sent: Sunday, March 17, 2024 2:44 PM
To: 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  于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
>>> , as its associated PR
>>>  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  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 
 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
>

Re: [DISCUSS] Towards Calcite 1.37.0

[Mihai Budiu]

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 
Sent: Sunday, March 17, 2024 2:44 PM
To: 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  于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
>>> , as its associated PR
>>>  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  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 
 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 
> wrote:
>>
>> With so many commits it's definitely a good time to cut a new
>>> release.
>>
>> I can be the RM for 

Re: Pull Request Reviews for Avatica

[Francis Chuang]

Going through the open PRs again (thanks to community members who 
reviewed and merged!), I think these are definitely candidates that can 
be merged for the 1.25.0 release:
- CALCITE-6282 - Avatica ignores time precision when returning TIME 
results [1]

- CALCITE-6248 - Illegal dates are accepted by casts [2]
- CALCITE-6137 - Upgrade Gradle from 8.1.1 to 8.5, support jdk21 [3]

This one also has some potential as I think there is consensus that's 
it's almost ready (with some minor changes):
- CALCITE-5964 - Add test case checking that 
connection.getMetaData().getTables() handles responses with different 
signature shapes. [4]


These are probably a stretch as there hasn't been consensus yet, but 
would be nice to have:

- CALCITE-6135 - BEARER authentication support [5]
- CALCITE-5534 - Add userAgent JDBC param [6]

These 3 are linked together and will probably need a significant amount 
of work:

- CALCITE-5535 - Properly truncate time values [7]
- CALCITE-5446 - Add support for TIMESTAMP WITH LOCAL TIME ZONE [8]
- CALCITE-5487 - Proper semantics for TIMESTAMP WITH LOCAL TIME ZONE [9]

Community members, please take a look at the PRs listed and review and 
merge if they are ready.


Francis

[1] https://github.com/apache/calcite-avatica/pull/241
[2] https://github.com/apache/calcite-avatica/pull/238
[3] https://github.com/apache/calcite-avatica/pull/234
[4] https://github.com/apache/calcite-avatica/pull/227
[5] https://github.com/apache/calcite-avatica/pull/232
[6] https://github.com/apache/calcite-avatica/pull/211
[7] https://github.com/apache/calcite-avatica/pull/210
[8] https://github.com/apache/calcite-avatica/pull/209
[9] https://github.com/apache/calcite-avatica/pull/205

On 12/03/2024 8:03 am, Francis Chuang wrote:
Going slightly off-topic: I can be RM for the next Avatica release to 
make this happen.


Francis

On 12/03/2024 4:38 am, Mihai Budiu wrote:
I haven't spent too much time trying to fix the CI problem, I was 
planning to spend some time on this, but this email triggered my 
response before I had time to investigate.


I have two PRs outstanding against Avatica which need fixes in both 
sides:


Illegal dates are accepted by casts
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6248
https://github.com/apache/calcite-avatica/pull/238

Avatica ignores time precision when returning TIME results
https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-6282
https://github.com/apache/calcite-avatica/pull/241

Mihai


From: Julian Hyde 
Sent: Monday, March 11, 2024 9:49 AM
To: dev@calcite.apache.org 
Subject: Re: Pull Request Reviews for Avatica

Mihai,

Can you list the PRs (jira cases) in this category?

I thought I suggested a solution. disable tests in Calcite based on 
the Avatica version number.  And make the changes just before an 
Avatica release, and quickly upgrade Calcite, so that any tests you 
need to disable aren’t disabled for long.


I’m sure most of the PRs that Francis refers to will not break 
Calcite, so there’s no reason to defer those.


Julian


On Mar 11, 2024, at 09:28, Mihai Budiu  wrote:

Some fixes in avatica require simultaneous fixes in Calcite - 
sometimes just tests that behave differently. I haven't figured out a 
good process that makes both CIs happy.


Mihai

From: Francis Chuang 
Sent: Saturday, March 9, 2024 9:18 PM
To: dev@calcite.apache.org 
Subject: Pull Request Reviews for Avatica

Hey everyone!

Looking at the open pull requests for Avatica [1], it seems that there
are a few that have been languishing for a while.

Some of them seem pretty uncontroversial and simple, but there are some
that will require further discussion (whether through the jira issue or
here on the list).

Can community members please spare some time to review some of the PRs
and commit them?

Francis

[1] https://github.com/apache/calcite-avatica/pulls

[jira] [Created] (CALCITE-6334) Release Avatica 1.25.0

[Francis Chuang (Jira)]

Francis Chuang created CALCITE-6334:
---

 Summary: Release Avatica 1.25.0
 Key: CALCITE-6334
 URL: https://issues.apache.org/jira/browse/CALCITE-6334
 Project: Calcite
  Issue Type: Task
Reporter: Francis Chuang
Assignee: Francis Chuang






--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Re: [DISCUSS] Towards Calcite 1.37.0

[Sergey Nuyanzin]

Hi Francis

thanks for letting know

I think it would makes sense to apply this changes to Avatica and then to
Calcite


On Mon, Mar 18, 2024 at 8:59 AM Xiong Duan  wrote:

> +1 It is a good time to release a new version.
>
> Francis Chuang  于2024年3月18日周一 05:44写道：
> >
> > 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  于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
> > >>> , as its
> associated PR
> > >>>  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 
> 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  >
> >  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.

Re: [DISCUSS] Towards Calcite 1.37.0

[Xiong Duan]

+1 It is a good time to release a new version.

Francis Chuang  于2024年3月18日周一 05:44写道：
>
> 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  于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
> >>> , as its associated PR
> >>>  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  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 
>  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 
> > 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,