I agree with Jacques: we should release after graduation. But I think we should get a release ready before graduation, including snapshots, stabilization, release candidates and an informal vote for a release candidate. All being well, we can start a formal vote as a top-level PMC on Oct 22nd, the day after the Board meeting.
Jesus goes on vacation soon after that, so but we basically will have the release in the bag by then. Julian On Mon, Oct 5, 2015 at 12:21 PM, Julian Hyde <[email protected]> wrote: > I still have some big pieces of work I'd like to get in before the > release: 816 (sub-query), 785 (piglet), 910 (improved handling of > ARRAY, MULTISET, STRUCT, MAP). I am developing 910 (along with other > issues related to multisets: 854, 879, 877) on the 785 branch. I will > check it in first, hopefully tomorrow. 785 will come soon after, and > then 816 in a few days. > > That said, it is worth making a snapshot tonight. The biggest API > change in the release, 828 (RelBuilder) is already in, and it would be > worth seeing whether Hive, Drill etc. can run against it. > > I have checked 909 and 906 into Apache master so you can make the > snapshot anytime you like. > > Julian > > * https://issues.apache.org/jira/browse/CALCITE-785 piglet > * https://issues.apache.org/jira/browse/CALCITE-816 sub-query > * https://issues.apache.org/jira/browse/CALCITE-828 RelBuilder > * https://issues.apache.org/jira/browse/CALCITE-854 UNNEST with ORDINALITY > * https://issues.apache.org/jira/browse/CALCITE-877 ROW as argument to > UNCOLLECT > * https://issues.apache.org/jira/browse/CALCITE-879 COLLECT > * https://issues.apache.org/jira/browse/CALCITE-909 Make > ReduceExpressionsRule extensible > * https://issues.apache.org/jira/browse/CALCITE-910 improve ARRAY, > MULTISET support > > > On Mon, Oct 5, 2015 at 3:38 AM, Jesus Camacho Rodriguez > <[email protected]> wrote: >> I still want to add CALCITE-909 to the release, it is just pending review. >> >> We didn't hear about any other pending issues, I guess we can move forward >> with the 1.5 release? Should we enter the stabilization period today i.e. >> freeze by the end of the day and create the first SNAPSHOT? >> >> Thanks, >> Jesús >> >> >> >> On 9/30/15, 8:24 PM, "Julian Hyde" <[email protected]> wrote: >> >>>Can someone comment on how long it will take to make a release after >>>graduating? >>> >>>On Wed, Sep 30, 2015 at 4:21 AM, Jesus Camacho Rodriguez >>><[email protected]> wrote: >>>> @Julian, sure, it will be nice to be the release manager for 1.5. >>>> >>>> If I understand well, once the vote to establish Calcite as a top-level >>>> project passes, there should be some work together with the Apache infra >>>> team to do the migration to top-level project, right? >>>> Thus, I think it makes sense to release 1.5 before that. How do others >>>> feel about all this? >>>> >>>> We could try to follow this tentative schedule: >>>> * October 2nd (Friday) - close MASTER, enter stabilization period >>>> * October 9th (Friday) - first release candidate >>>> * October 16th (Friday) - release >>>> >>>> >>>> About pending patches: on my side, I plan to review CALCITE-900 today so >>>> it can go in. I will try to include CALCITE-856 too. >>>> >>>> Thanks, >>>> Jesús >>>> >>>> >>>> On 9/29/15, 7:16 PM, "Julian Hyde" <[email protected]> wrote: >>>> >>>>>When would be a good time for our next release? >>>>> >>>>>Here are some dates: >>>>>* We aim to release "every month or so". >>>>>* 1.4 was released on 9/2 [1]. >>>>>* It takes about 2 weeks to release, so if we started today, we could >>>>>release on about 10/13. >>>>>* The Apache board meeting is on 10/14 [2] and if the vote to >>>>>establish Calcite passes we would make our first release as a >>>>>top-level project as early as 10/21. >>>>> >>>>>Does anyone have any other constraints, e.g. features they would like >>>>>to complete? >>>>> >>>>>Jesus, could you take on the release manager role? >>>>> >>>>>Julian >>>>> >>>>>[1] http://calcite.incubator.apache.org/docs/history.html#v1-4-0 >>>>>[2] http://www.apache.org/foundation/board/calendar.html >>>>> >>>> >>>
