I am in favor of postponing too. We said “end of August” but mid-September would be fine, especially if we are able to include a significant number of improvements to the Druid adapter.
I think the next release should be called 1.10.0. 2.0 would be a major release[1] (including non-compatible API changes, and removing deprecated APIs) and I don’t think we need a major release just yet. I agree that it would be 1 - 2 months after 1.9.0, and should include Avatica 1.9.0. Julian [1] http://semver.org/ <http://semver.org/> > On Sep 1, 2016, at 12:14 PM, Jesus Camacho Rodriguez > <jcamachorodrig...@hortonworks.com> wrote: > > I am thinking on postponing the first RC (till next week). Monday is holiday > in US, thus I think there is little value on starting the vote tomorrow and > need to extend the vote for additional couple of days. Plus there are still a > couple of pending JIRA issues that we wanted to check in before the release > but are not ready yet (see CALCITE-1356). > > If somebody is really eager to have 1.9.0 asap, the alternative is to cut the > first RC now, and maybe we could have a 2.0.0 quickly after that (3-4 week > time span), which would contain fixes for the remaining issues. > > I am in favor of postponing. Feedback is appreciated! > > > Thanks, > Jesús > > @Atri, thanks for the help. Did you get to run the full regression suite? If > you do and find any issues, please create new JIRA cases and link them to > CALCITE-1356. > > > > On 8/31/16, 10:48 PM, "Julian Hyde" <jh...@apache.org> wrote: > >> Atri, >> >> I think it would be useful if you ran the full regression tests (integration >> tests). They don’t get run very often and I noticed that there was an error >> from the Druid suite. There might be others. You’ll need to get the VM >> running. >> >> Julian >> >>> On Aug 30, 2016, at 12:00 PM, Atri Sharma <atri.j...@gmail.com> wrote: >>> >>> Hi Jesus, >>> >>> Please let me know where I can help in this. >>> >>> On 31 Aug 2016 12:30 a.m., "Jesus Camacho Rodriguez" < >>> jcamachorodrig...@hortonworks.com> wrote: >>> >>>> Hi team, >>>> >>>> I have updated CALCITE-1356 with a list of the issues that are still open >>>> and we wanted to include in 1.9.0, and their status. >>>> >>>> We plan to cut the first RC by the end of this week. Please, if you want >>>> to include any other issue in the release, push it before then! >>>> >>>> Thanks. >>>> >>>> >>>> >>>> On 8/24/16, 8:34 PM, "Julian Hyde" <jh...@apache.org> wrote: >>>> >>>>> Thanks, Jesus. As Atri has also volunteered to help, can you work with >>>> him. >>>>> >>>>> If you add issues that you would like to be in 1.9, please indicate who >>>> is going to do the work! Obviously we’d all like the issues we logged to be >>>> fixed as soon as possible, but as my wife always says, she’d love a free >>>> trip to Fiji. >>>>> >>>>> Julian >>>>> >>>>> >>>>>> On Aug 23, 2016, at 11:39 PM, Jesus Camacho Rodriguez < >>>> jcamachorodrig...@hortonworks.com> wrote: >>>>>> >>>>>> Thanks for pushing a new release Julian. If there are no objections, >>>>>> I can be the release manager for 1.9. >>>>>> >>>>>> I will log the issues that I would like to go in before the release in >>>>>> CALCITE-1356. I suggest everybody does the same! >>>>>> >>>>>> >>>>>> Thanks, >>>>>> Jesús >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On 8/24/16, 4:42 AM, "Atri Sharma" <a...@apache.org <mailto: >>>> a...@apache.org>> wrote: >>>>>> >>>>>>> For sure, I will be on it >>>>>>> >>>>>>> On Wed, Aug 24, 2016 at 1:56 AM, Julian Hyde <jh...@apache.org >>>> <mailto:jh...@apache.org>> wrote: >>>>>>> >>>>>>>> Unfortunately, the release manager has to be a committer. There are >>>>>>>> practical reasons (you need write access to several ASF systems) and >>>> legal >>>>>>>> ones (you are making the release on behalf of Apache). >>>>>>>> >>>>>>>> That said, I very much appreciate your offer to help. Could you help >>>> with >>>>>>>> the logistics? For example compiling release notes, running test >>>> builds, >>>>>>>> and chasing up the various JIRA cases and pull requests that are >>>> required >>>>>>>> in the release. >>>>>>>> >>>>>>>> The release instructions[1] describe the pre-release checks that need >>>> to >>>>>>>> be performed. If you did those the actual release would run more >>>> smoothly. >>>>>>>> >>>>>>>> Julian >>>>>>>> >>>>>>>> [1] https://calcite.apache.org/docs/howto.html#making-a- >>>>>>>> release-for-calcite-committers <https://calcite.apache.org/ < >>>> https://calcite.apache.org/> >>>>>>>> docs/howto.html#making-a-release-for-calcite-committers> >>>>>>>> >>>>>>>>> On Aug 23, 2016, at 10:44 AM, Atri Sharma <a...@apache.org> wrote: >>>>>>>>> >>>>>>>>> I can be the release manager (my first time,so would need support and >>>>>>>>> bootstrapping, but would love to help). >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Atri >>>>>>>>> >>>>>>>>> On Tue, Aug 23, 2016 at 11:11 PM, Julian Hyde <jh...@apache.org> >>>> wrote: >>>>>>>>> >>>>>>>>>> It’s time to start work on Calcite release 1.9, so we can hit the >>>> “end >>>>>>>> of >>>>>>>>>> August” target. >>>>>>>>>> >>>>>>>>>> Does this timeline (end of August) still work for everyone? >>>>>>>>>> >>>>>>>>>> Would anyone like to be release manager? >>>>>>>>>> >>>>>>>>>> Are there any issues that people would like to get into 1.9 (and are >>>>>>>>>> prepared to work on)? >>>>>>>>>> >>>>>>>>>> It should be quite a straightforward release. I have logged >>>>>>>>>> https://issues.apache.org/jira/browse/CALCITE-1356 < >>>>>>>>>> https://issues.apache.org/jira/browse/CALCITE-1356> to track. >>>>>>>>>> >>>>>>>>>> Julian >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Atri >>>>>>>>> Apache Concerted >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Regards, >>>>>>> >>>>>>> Atri >>>>>>> Apache Concerted >>>>> >>>> >> >>
