Thanks for volunteering, Haisheng.

Before everyone piles in with wish-lists, can we set a timescale for the 
release? 

I would suggest an aggressive timescale, for example an RC a week from today. 
Hold the RC only for mandatory cases. Other stuff gets in if it’s ready. 

Julian

> On May 5, 2020, at 5:51 AM, Ruben Q L <[email protected]> wrote:
> 
> Thanks for starting the discussion, Stamatis.
> 
> Just a reminder that there is a blocking issue [1] that needs to be solved
> (it is a regression introduced after 1.22).
> Apart from that, it would be nice if we could include [2] in 1.23.
> 
> Best regards,
> Ruben
> 
> [1] https://issues.apache.org/jira/browse/CALCITE-3926
> [2] https://issues.apache.org/jira/browse/CALCITE-3951
> 
> 
> 
>> Le mar. 5 mai 2020 à 12:34, Roman Kondakov <[email protected]> a
>> écrit :
>> 
>> Hi Haisheng,
>> 
>> I would like to review CALCITE-3896. Do you have a PR?
>> 
>> 
>> --
>> Kind Regards
>> Roman Kondakov
>> 
>> 
>>> On 05.05.2020 06:37, Haisheng Yuan wrote:
>>> IIRC, I am the release manager for 1.23.0.
>>> 
>>> I think CALCITE-3896 (top-down trait request) is in good shape, it will
>> be nice if it can go into 1.23.0. Can someone help review?
>>> 
>>> On 2020/05/04 22:58:25, Stamatis Zampetakis <[email protected]> wrote:
>>>> Hello,
>>>> 
>>>> Calcite 1.22.0 was released about 2 months ago (on March 5, 2020).
>> During
>>>> the vote we said to try to have a release sooner than usual so I am
>>>> launching the discussion now hoping we could get to 1.23.0 rather soon.
>>>> 
>>>> I was checking the status of the current release [1] and we have already
>>>> over 100 resolved issues with 91 fixes so it is already pretty big.
>>>> 
>>>> I know that there quite a few discussions in progress so it would be
>> good
>>>> to see how many of the ongoing cases should be fixed for 1.23.0.
>>>> 
>>>> More importantly do we have a release manager for 1.23.0?
>>>> 
>>>> Best,
>>>> Stamatis
>>>> 
>>>> [1]
>>>> 
>> https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333950
>>>> 
>> 

Reply via email to