Hi Jesus, Please let me know where I can help in this.
On 31 Aug 2016 12:30 a.m., "Jesus Camacho Rodriguez" < [email protected]> 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" <[email protected]> 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 < > [email protected]> 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" <[email protected] <mailto: > [email protected]>> wrote: > >> > >>> For sure, I will be on it > >>> > >>> On Wed, Aug 24, 2016 at 1:56 AM, Julian Hyde <[email protected] > <mailto:[email protected]>> 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 <[email protected]> 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 <[email protected]> > 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 > > >
