Here is the latest status of 1.8.0 release.

(venki) DRILL-4732, DRILL-4729, DRILL-4728 : merged
(sudheesh) DRILL-4822, DRILL-4819, DRILL-4623 : merged
DRILL-4792 : not merged.

DRILL-4836 was opened just now, which seems to be a regression from
several release back. I think it would make sense to try to get
DRILL-4836 fixed in this release.

I'll also try to merge Dave's DRILL-4704 tonight.


On Fri, Aug 5, 2016 at 1:35 PM, Venki Korukanti
<venki.koruka...@gmail.com> wrote:
> I will try to get these sometime today or eod tomorrow.
>
> 1) DRILL-4728: Add support for new metadata fetch APIs,
> https://github.com/apache/drill/pull/527 (Ready to commit after few minor
> changes)
>
> 2) DRILL-4729: Add support for prepared statement API on server side,
> https://github.com/apache/drill/pull/530 (need to address a review comment)
>
> 3) DRILL-4732: Update JDBC driver to use new prepared statement API in
> DrillClient, https://github.com/apache/drill/pull/532 (need to address a
> comment).
>
> Thanks
> Venki
>
> On Fri, Aug 5, 2016 at 1:31 PM, Sudheesh Katkam <skat...@maprtech.com>
> wrote:
>
>> Yes, that’s a typo. DRILL-3623 was for LIMIT 0 changes. That number will
>> forever remain in my subconscious ;)
>>
>> Thank you,
>> Sudheesh
>>
>> > On Aug 5, 2016, at 1:27 PM, Zelaine Fong <zf...@maprtech.com> wrote:
>> >
>> > I assume #3 has a typo.  It should be DRILL-4623.
>> >
>> > -- Zelaine
>> >
>> > On Fri, Aug 5, 2016 at 1:15 PM, Sudheesh Katkam <sudhe...@apache.org>
>> wrote:
>> >
>> >> Here’s my list that I will try to get in before Monday.
>> >>
>> >> 1) DRILL-4822: Pending commit.
>> >> PR: https://github.com/apache/drill/pull/558
>> >>
>> >> 2) DRILL-4819: Pending review from Aditya.
>> >> PR: https://github.com/apache/drill/pull/556
>> >>
>> >> 3) DRILL-3623: Pending tests (or test results).
>> >> PR: https://github.com/apache/drill/pull/486
>> >>
>> >> 4) DRILL-4792: Pending changes from Arina.
>> >> PR: https://github.com/apache/drill/pull/551
>> >>
>> >> The first three will make it; the last one may not.
>> >>
>> >> Thank you,
>> >> Sudheesh
>> >>
>> >>
>> >> On Wed, Aug 3, 2016 at 11:49 AM, Jinfeng Ni <jinfengn...@gmail.com>
>> wrote:
>> >>
>> >>> I would like to propose we set Monday 8/8 as the tentative cut-off
>> >>> date for 1.8 release.
>> >>>
>> >>> If people have any working-in-progress patches, and would like to
>> >>> include in 1.8 release, please submit PR, or ping people to review
>> >>> your PR if there has been a PR under review.
>> >>>
>> >>> Thanks,
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Aug 2, 2016 at 3:00 PM, Jinfeng Ni <jinfengn...@gmail.com>
>> >> wrote:
>> >>>> Hello everyone,
>> >>>>
>> >>>>  I would like to start the train for 1.8 release.
>> >>>>
>> >>>>  If you have been working on some open issues, and want to include
>> >>>> them in 1.8, please rely this email and let us know the JIRAs number
>> >>>> and corresponding pull requests.
>> >>>>
>> >>>>  Based on the response, we may go through the list of opens JIRAs for
>> >>>> 1.8, and come up with a tentatively cut-off date for 1.8 release.
>> >>>>
>> >>>>  Thanks,
>> >>>>
>> >>>>
>> >>>>
>> >>>> On Tue, Aug 2, 2016 at 2:14 PM, Aditya <a...@apache.org> wrote:
>> >>>>> +1 for Jinfeng as the RM for 1.8 release.
>> >>>>>
>> >>>>> On Tue, Aug 2, 2016 at 11:59 AM, Jinfeng Ni <jinfengn...@gmail.com>
>> >>> wrote:
>> >>>>>
>> >>>>>> I'll volunteer to be the release manager for 1.8, if no one else
>> >> would
>> >>>>>> like to do so.
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> On Mon, Aug 1, 2016 at 9:40 PM, Parth Chandra <par...@apache.org>
>> >>> wrote:
>> >>>>>>> Hi Everyone,
>> >>>>>>>
>> >>>>>>>   I think its time to roll out 1.8.  Would any PMC
>> >> member/committer
>> >>>>>> like
>> >>>>>>> to volunteer to be the release manager?
>> >>>>>>>
>> >>>>>>> Parth
>> >>>>>>
>> >>>
>> >>
>>
>>

Reply via email to