calcite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesus Camachorodriguez <jcamachorodrig...@hortonworks.com>
Subject Re: Timing for Calcite 1.3 release
Date Tue, 05 May 2015 10:01:31 GMT
I'll take care of the issue on my side by Friday so it can be included in
1.3.

Jesús


On 4/30/15, 8:04 PM, "Nick Dimiduk" <ndimiduk@gmail.com> wrote:

>Sorry, I've been off wrangling an HBase release and the intricate details
>of wiring the Phoenix query server into Ambari. Let me take a look at
>these
>in the next couple days.
>
>On Wed, Apr 29, 2015 at 4:59 PM, Julian Hyde <julian@hydromatic.net>
>wrote:
>
>> PS The issues flagged for "next release" include some assigned to
>> Jesus & Nick.
>> 
>>https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%
>>20fixVersion%20%3D%20%22next%22
>>
>> On Wed, Apr 29, 2015 at 4:45 PM, Julian Hyde <jhyde@apache.org> wrote:
>> > When would be a good time for to make 1.3? Calcite 1.2 was baked on
>> > April 7th and announced on April 17th. How about we aim for this:
>> >
>> > * May 8th (Friday) - enter stabilization (see below)
>> > * May 12th (Tuesday) - first release candidate
>> > * May 22nd (Friday) - release announcement
>> >
>> > If dependent projects would like a different schedule, please speak
>>up.
>> >
>> > I'd like to try a different QA process this release. Recall that last
>> > time, Vladimir discovered an issue with time zones on the first
>> > release candidate. I'd like to discover issues like that before we
>> > move to an RC vote.
>> >
>> > I propose that we have a stabilization period, during which, each
>> > stakeholder would validate the release and log any issues they find as
>> > jira cases. For example, Vladimir would pull the latest and run the
>> > test suite in the Moscow time zone. Nick would run through Phoenix
>> > tests. And so forth. I'd push a new snapshot at the start of the
>> > stabilization period, but people can test on any commit that happens
>> > after that.
>> >
>> > I propose that we enter stabilization on Friday May 8th.
>> >
>> > Would anyone like to be release manager? (He asked with a sigh.)
>> >
>> > Let's hear +1 or -1 for this schedule and the proposed stabilization
>> process.
>> >
>> > Julian
>>


Mime
View raw message