Re: Towards Calcite release 1.11

[Julian Hyde <jh...@apache.org>]

I’ve made progress on 1494, but not fast enough to make it into the release.

I’ve started a vote on RC0. Please review the release and cast your vote.

Until the release passes, please do not make commits to master branch.

Julian


> On Dec 29, 2016, at 8:11 AM, Julian Hyde <jh...@apache.org> wrote:
> 
> Yesterday (Dec 28th) was the target for the first release candidate, but I missed it. I still have one JIRA case to finish (1494). I hope to finish it today, and make a release candidate.
> 
> Jesus, have you made any progress on your cases?
> 
> See https://issues.apache.org/jira/browse/CALCITE-1547 <https://issues.apache.org/jira/browse/CALCITE-1547> for more details.
> 
> Julian
> 
> 
>> On Dec 22, 2016, at 3:52 PM, Julian Hyde <jhyde@apache.org <ma...@apache.org>> wrote:
>> 
>> Would it be useful if I push a snapshot of Calcite’s master branch, so that downstream projects (e.g. Solr, Storm, Hive) can make sure that it doesn’t break anything? I’d do it a few days before the first RC, to give you time to run your test suites against it.
>> 
>> Julian
>> 
>> 
>>> On Dec 20, 2016, at 9:16 AM, Julian Hyde <jhyde@apache.org <ma...@apache.org>> wrote:
>>> 
>>> Great, thanks Jesus.
>>> 
>>> I’ve logged https://issues.apache.org/jira/browse/CALCITE-1547 <https://issues.apache.org/jira/browse/CALCITE-1547> to track the release.
>>> 
>>> Julian
>>> 
>>>> On Dec 20, 2016, at 5:13 AM, Jesus Camacho Rodriguez <jcamacho@apache.org <ma...@apache.org>> wrote:
>>>> 
>>>> Julian,
>>>> 
>>>> I will try to push 1456 and 1413 before Wed 28th (1421 is just site documentation update), please do not defer them to next release yet. However, if they are not pushed on time, feel free to do so.
>>>> 
>>>> Thanks,
>>>> Jesús
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On 12/19/16, 8:13 PM, "Julian Hyde" <jhyde@apache.org <ma...@apache.org>> wrote:
>>>> 
>>>>> So, I’m hearing that we should make a release soonish. I propose code freeze by Wed 28th (9 days from now), hopefully release in 1st or 2nd week of January. Does that sound reasonable?
>>>>> 
>>>>> Does anyone volunteer to be a release manager? I’d rather not be release manager again, but I’ll do it if no one else wants to.
>>>>> 
>>>>> What issues remain?
>>>>> * I am working on a few sub-query issues (1511, 1537, 1494).
>>>>> * Jesus: You have 1456, 1421, 1413 assigned to you and marked fixVersion = 1.11.0. Do you intend to fix these?
>>>>> * Is anyone working on cases that must be in 1.11? If so, speak up now. We can hold the release if you need more time, but only for a short time.
>>>>> * (If you would like an issue fixed for 1.11 but are not prepared to work on it I’m not very interested in hearing about it. Sorry.)
>>>>> 
>>>>> What issues are ready to review?
>>>>> * There are pull requests for 1540, 1414.
>>>>> * Maryann: There are several pull requests from you that I think you have committed already[1]. Can you close those PRs? (If a committer commits a non-committer’s pull request, they add “Close apache/calcite#NNN” to the commit comments, so that the PR gets closed, but this didn’t happen because you committed directly.) 
>>>>> 
>>>>> Is there any work for 1.11 that is not yet captured by a JIRA case?
>>>>> 
>>>>> Julian
>>>>> 
>>>>> [1] https://github.com/apache/calcite/pulls <https://github.com/apache/calcite/pulls><https://github.com/apache/calcite/pulls <https://github.com/apache/calcite/pulls>>
>>>>> 
>>>>>> On Dec 19, 2016, at 10:04 AM, Kevin Risden <compuwizard123@gmail.com <ma...@gmail.com>> wrote:
>>>>>> 
>>>>>> Solr (SOLR-8593) is waiting on 1.11 as well.
>>>>>> 
>>>>>> Kevin Risden
>>>>>> 
>>>>>> On Thu, Dec 15, 2016 at 12:09 AM, Arun Mahadevan <arunm@apache.org <ma...@apache.org>> wrote:
>>>>>> 
>>>>> 
>>>>>>> +1 for releasing 1.11 ASAP. It has some fixes that Apache Storm
>>>>>>> (storm-sql) is waiting on.
>>>>>>> 
>>>>>>> Thanks,
>>>>>>> Arun
>>>>>>> 
>>>>>>> On 12/15/16, 3:21 AM, "Julian Hyde" <jhyde@apache.org <ma...@apache.org>> wrote:
>>>>>>> 
>>>>>>>> When should we be targeting to release Calcite version 1.11?
>>>>>>>> 
>>>>>>>> Last release (1.10) was 12th October. Usually we release every 2 months,
>>>>>>> so we’re already overdue. Since 1.10 we’ve had 76 commits, and about 60 bug
>>>>>>> fixes (not counting Avatica work).
>>>>>>>> 
>>>>>>>> What bug fixes/features would people like to contribute to the release?
>>>>>>> What are your time constraints?
>>>>>>>> 
>>>>>>>> Julian
>>> 
>> 
>