erting 3154708 is here:
> > >>>>>>>>>>>
> > >>>>>>>>>>
> > >>>>>>> https://github.com/apache/calcite/commit/213c13776651f83f95dceb9645a15e940ec6dce1
> > >>>>>>>>
m/apache/calcite/commit/213c13776651f83f95dceb9645a15e940ec6dce1
> >>>>>>>>>>>
> >>>>>>>>>>> Let me know if I can do anything else to help and thank y'all for
> >>>>>>>>>> handling
> >>>>>>>>>>> the release!
> >>>>>>>>>>>
>
_
From: Benchao Li
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org
Subject: Re: [DISCUSS] Towards Calcite 1.36.0
Due to the inactivity of the review for CALCITE-5884 and
CALCITE-4455,
I think we can move it out of 1.36.0 for now. What do you
t;>
> > >>>>>>>>> On Tue, Nov 7, 2023 at 6:34 PM Tanner Clary
> > >>>>>>>>>
> > >>>>>>>> wrote:
> > >>>>>>>>>
> > >>>>>>>>>> I can re
;>>>> francischu...@apache.org>
> >>>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> I believe the main branch should still be frozen as we're still
> >>>>>>>> voting
> >>
___
From: Benchao Li
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org
Subject: Re: [DISCUSS] Towards Calcite 1.36.0
Due to the inactivity of the review for CALCITE-5884 and
CALCITE-4455,
I think we can move it out of 1.36.0 for now. What do you
think?
Othe
> Hi, Benchao
> >>>>>>>>>>
> >>>>>>>>>> Is the main branch still frozen?
> >>>>>>>>>>
> >>>>>>>>>> I found a new commit[1], but 1.36.0 has not been released.
>
1月1日周三 02:42写道：
5884 is mostly documentation fixes.
I expected it would be easy to get it in.
But we can leave it for later.
Mihai
From: Benchao Li
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org
Subject: Re: [DISCUSS] Towards Calci
3505
> > >>>>>>>>
> > >>>>>>>> Benchao Li 于2023年11月6日周一 12:46写道：
> > >>>>>>>>>
> > >>>>>>>>> Hi devs,
> > >>>>>>>>>
> > >>>>>>>&
; start the
> >>>>>>>>> release process now. Therefore main branch is in code freeze
> >>> until
> >>>>>>>>> further notice.
> >>>>>>>>>
> >>>>>>>>> Benchao Li 于2023年11
we can leave it for later.
Mihai
From: Benchao Li
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org
Subject: Re: [DISCUSS] Towards Calcite 1.36.0
Due to the inactivity of the review for CALCITE-5884 and
CALCITE-4455,
I think we can move it out of 1
>>
>> > >> >>>> LakeShen 于2023年11月1日周三 12:13写道：
>> > >> >>>>>
>> > >> >>>>> Hi Itiel,
>> > >> >>>>>
>> > >> >>>>> I have revi
三 12:13写道：
> > >> >>>>>
> > >> >>>>> Hi Itiel,
> > >> >>>>>
> > >> >>>>> I have reviewd the
> https://github.com/apache/calcite/pull/3325,and
> > >> >> left one
> > >> >>>>> comments
> > >> >>
t; >>>>>>>>>> Hi, all:
> >> >>>>>>>>>> We're already very close to 1.36.0, all unresolved issues
> >> >> has been
> >> >>>>>> someone
> >> >>>>>>>>>&g
chao Li 于2023年11月1日周三 10:17写道：
>> >>>>>
>> >>>>>> Mihai,
>> >>>>>> I've reviewed 5884, it looks good and I think we can have it in
>> >> 1.36.0
>> >>>>>>
>> >>>>>> Itiel,
>> >>>>>> https://github.com/ap
gt;>>>> I've reviewed 5884, it looks good and I think we can have it in
> > >> 1.36.0
> > >>>>>>
> > >>>>>> Itiel,
> > >>>>>> https://github.com/apache/calcite/pull/3325 has been reviewed and
> > >
>>> Itiel,
> >>>>>> https://github.com/apache/calcite/pull/3325 has been reviewed and
> >> even
> >>>>>> with an approval, I'll try to ping in the PR to try to get it
> >> merged
> >>>>>> in
it for later.
Mihai
From: Benchao Li
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org
Subject: Re: [DISCUSS] Towards Calcite 1.36.0
Due to the inactivity of the review for CALCITE-5884 and
CALCITE-4455,
I think we can move it out of 1.36.0 for now
th an approval, I'll try to ping in the PR to try to get it
> merged
> > > > > in 1.36.0
> > > > >
> > > > > Mihai Budiu 于2023年11月1日周三 02:42写道：
> > > > > >
> > > > > > 5884 is mostly documentation fixes.
> &g
t; > >
> > > > Mihai Budiu 于2023年11月1日周三 02:42写道：
> > > > >
> > > > > 5884 is mostly documentation fixes.
> > > > > I expected it would be easy to get it in.
> > > > > But we can leave it for later.
> > > >
/jira/browse/CALCITE-6052
> > > > > >>
> > > > > >> #3. Last update exceeded 7 days
> > > > > >> https://issues.apache.org/jira/browse/CALCITE-5884
> > > > > >> https://issues.apache.org/jira/browse/CALCITE-6037
> > > > > >>
> > &g
________________
> > > From: Benchao Li
> > > Sent: Tuesday, October 31, 2023 6:50 AM
> > > To: dev@calcite.apache.org
> > > Subject: Re: [DISCUSS] Towards Calcite 1.36.0
> > >
> > > Due to the inactivity of the review for CALC
; > But we can leave it for later.
> >
> > Mihai
> >
> >
> > From: Benchao Li
> > Sent: Tuesday, October 31, 2023 6:50 AM
> > To: dev@calcite.apache.org
> > Subject: Re: [DISCUSS] Towards Calcite 1.36.0
> >
> > Due to the inactivity of th
mostly documentation fixes.
> I expected it would be easy to get it in.
> But we can leave it for later.
>
> Mihai
>
>
> From: Benchao Li
> Sent: Tuesday, October 31, 2023 6:50 AM
> To: dev@calcite.apache.org
> Subject: Re: [DIS
5884 is mostly documentation fixes.
I expected it would be easy to get it in.
But we can leave it for later.
Mihai
From: Benchao Li
Sent: Tuesday, October 31, 2023 6:50 AM
To: dev@calcite.apache.org
Subject: Re: [DISCUSS] Towards Calcite 1.36.0
Due
> >>>
> > >>> Mihai Budiu 于2023年10月25日周三 05:02写道：
> > >>>>
> > >>>> For the blocker issues, I have filed two PRs which should
> collectively
> > >>> fix them.
> > >>>>
> > >>>> https://github.com/apache/calcite/pull/3481 fixes
> >
se/CALCITE-5990, but does not include
> >>> tests, because the test fixture needs to be fixed as well for the tests
> >> to
> >>> pass. There are tests in the next PR:
> >>>> https://github.com/apache/calcite/pull/3471 fixes
> >>> https://issue
ITE-5990, but does not include
>>> tests, because the test fixture needs to be fixed as well for the tests
>> to
>>> pass. There are tests in the next PR:
>>>> https://github.com/apache/calcite/pull/3471 fixes
>>> https://issues.apache.org/jira/browse/CALCITE-
e fixed as well for the tests
> to
> > pass. There are tests in the next PR:
> > > https://github.com/apache/calcite/pull/3471 fixes
> > https://issues.apache.org/jira/browse/CALCITE-5921, but should be
> amended
> > to reenable the disabled tests if we merge 3481 fir
> Mihai
> >
> >
> > From: Benchao Li
> > Sent: Tuesday, October 24, 2023 5:46 AM
> > To: dev@calcite.apache.org
> > Subject: Re: [DISCUSS] Towards Calcite 1.36.0
> >
> > A quick update on the current status for i
ed to
> reenable the disabled tests if we merge 3481 first.
>
> Mihai
>
>
> From: Benchao Li
> Sent: Tuesday, October 24, 2023 5:46 AM
> To: dev@calcite.apache.org
> Subject: Re: [DISCUSS] Towards Calcite 1.36.0
>
> A quick update on
AM
To: dev@calcite.apache.org
Subject: Re: [DISCUSS] Towards Calcite 1.36.0
A quick update on the current status for issues targeted 1.36.0
We need more reviewers for #2 and #3 since the end of October is approaching.
Please correct me if I'm mistaken, especially for issues in #1.
#1. Issues
A quick update on the current status for issues targeted 1.36.0
We need more reviewers for #2 and #3 since the end of October is approaching.
Please correct me if I'm mistaken, especially for issues in #1.
#1. Issues already have reviewers, and seems promising to be merged shortly
Hi, community.
Recently I reported an issue[1] which revealed that calcite's MAP SubQuery
doesn't work,
considering this is a feature regression or bug, maybe we can fix it in
1.36.
The PR is ready. If someone has time, pls help to review it. many thanks.
[1]
From: Benchao Li
> > Sent: Saturday, October 7, 2023 8:01 PM
> > To: dev@calcite.apache.org
> > Cc: mbu...@gmail.com
> > Subject: [DISCUSS] Towards Calcite 1.36.0
> >
> > It's been a bit more than 2 months since our last release [1] and
> > there are curre
le to get them in for 1.36.
>
> Thank you for your patience.
> Mihai
>
> [1] https://github.com/apache/calcite/pull/3471
>
> From: Benchao Li
> Sent: Saturday, October 7, 2023 8:01 PM
> To: dev@calcite.apache.org
> Cc: mbu...@gmail.co
From: Benchao Li
Sent: Saturday, October 7, 2023 8:01 PM
To: dev@calcite.apache.org
Cc: mbu...@gmail.com
Subject: [DISCUSS] Towards Calcite 1.36.0
It's been a bit more than 2 months since our last release [1] and
there are currently 90+ new commits in main branch
I've created the https://issues.apache.org/jira/browse/CALCITE-6047 to
track the releasing staff.
Julian Hyde 于2023年10月12日周四 04:32写道：
>
> Thanks for volunteering, Benchao. Could you log a jira case for 1.36? Then
> people can cases to it. (As RM, you can remove unlink any cases you think
>
Thanks for volunteering, Benchao. Could you log a jira case for 1.36? Then
people can cases to it. (As RM, you can remove unlink any cases you think will
not be ready in time.)
> On Oct 11, 2023, at 3:29 AM, Ran Tao wrote:
>
> Thanks Benchao for opening this discussion!
>
> Maybe we can add
Thanks Benchao for opening this discussion!
Maybe we can add https://issues.apache.org/jira/browse/CALCITE-5918 in
1.36.0 ?
Currently it needs additional +1 review from the committer.
And I am willing to participate in the review of the remaining PRs of
1.36.0 (in familiar modules or sections)
...@gmail.com
Subject: [DISCUSS] Towards Calcite 1.36.0
It's been a bit more than 2 months since our last release [1] and there are
currently 90+ new commits in main branch.
As usual, according to our Jira dashboard [2] and Github [3], there are many
pending issues that could / should be part
+1,thanks,benchao.
I am willing to participate in the review of the remaining PRs of 1.36.0.
Best,
LakeShen
Benchao Li 于2023年10月8日周日 11:02写道：
> It's been a bit more than 2 months since our last release [1] and
> there are currently 90+ new commits in main branch.
>
> As usual, according to our
It's been a bit more than 2 months since our last release [1] and
there are currently 90+ new commits in main branch.
As usual, according to our Jira dashboard [2] and Github [3], there
are many pending issues that could / should be part of the release.
I'd propose to make a collective effort to
43 matches
Mail list logo
