Timing for Calcite 1.3 release

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

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

Re: Timing for Calcite 1.3 release

[Jesus Camachorodriguez <jc...@hortonworks.com>]

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" <nd...@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 <ju...@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 <jh...@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
>>

Re: Timing for Calcite 1.3 release

[Nick Dimiduk <nd...@gmail.com>]

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 <ju...@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 <jh...@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
>

Re: Timing for Calcite 1.3 release

[Julian Hyde <ju...@hydromatic.net>]

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 <jh...@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

Re: Timing for Calcite 1.3 release

[Julian Hyde <ju...@gmail.com>]

It's May 8th, so that means we're entering the stabilization phase for
release 1.3. This means:
* If you are a committer, don't check in changes that might break
something. Cosmetic changes are OK, and bug fixes are OK, as long as
they are reviewed.
* If you have a project that depends on Calcite, or otherwise have
some tough tests you can run, now is a great time to validate the
release. Download and build from master, and log bugs if you encounter
problems.

Once we've fixed the important issues discovered from that testing,
we'll create the first release candidate and a vote. If people do some
testing during the stabilization period, there is a good chance that
the RC1 will pass muster. Let's aim for Tue 12th for RC1.

Julian


On Wed, Apr 29, 2015 at 4:45 PM, Julian Hyde <jh...@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