Who should I add as a reviewer for 7032?
> On Mar 14, 2019, at 19:42, Sorabh Hamirwasia <sohami.apa...@gmail.com> wrote:
>
> Hi Charles,
> Can you please add reviewer for DRILL-7032 ?
> For DRILL-6970 the PR is closed by the author, I have pinged in JIRA asking
> to re-open so that it can be reviewed.
>
> Thanks,
> Sorabh
>
> On Thu, Mar 14, 2019 at 4:29 PM Charles Givre <cgi...@gmail.com> wrote:
>
>> Hi Sorabh,
>> I have 3 PRs that are almost done, awaiting final review. Drill-7077,
>> DRILL-7032, DRILL-7021. I owe @ariina some fixes for 7077, but I’m waiting
>> for review of the others. Also, there is that DRILL-6970 about the buffer
>> overflows in the logRegex reader that isn’t mine but I’d like to see
>> included.
>> Thanks,
>> —C
>>
>>> On Mar 14, 2019, at 13:13, Sorabh Hamirwasia <sohami.apa...@gmail.com>
>> wrote:
>>>
>>> Hi Arina,
>>> Thanks for your response. With ETA of two weeks we are looking at end of
>>> the month or beginning next month. I will wait until Monday for others to
>>> respond and then will finalize on a cut-off date.
>>>
>>> Thanks,
>>> Sorabh
>>>
>>> On Wed, Mar 13, 2019 at 4:28 AM Arina Ielchiieva <
>> arina.yelchiy...@gmail.com>
>>> wrote:
>>>
>>>> Hi Sorabh,
>>>>
>>>> thanks for volunteering to do the release.
>>>>
>>>> Paul and I are working on file schema provisioning for text file storage
>>>> which is aimed for 1.16. To wrap up the work we need to deliver two
>> Jiras:
>>>> DRILL-7095 and DRILL-7011. ETA: 2 weeks.
>>>> Please plan the release date accordingly.
>>>>
>>>> Kind regards,
>>>> Arina
>>>>
>>>> On Tue, Mar 12, 2019 at 9:16 PM Sorabh Hamirwasia <
>> sohami.apa...@gmail.com
>>>>>
>>>> wrote:
>>>>
>>>>> Hi All,
>>>>> It's around two and a half month since we did 1.15.0 release for Apache
>>>>> Drill. Based on our 3 months release cadence I think it's time to
>> discuss
>>>>> our next release. I will volunteer to manage the next release.
>>>>>
>>>>> **Below is the current JIRA stats:*
>>>>> *[1] Open#: 15*
>>>>>
>>>>> - Would be great if everyone can look into their assigned tickets and
>>>>> update the fix version as needed. Please keep the ones which you find
>>>>> must
>>>>> have and can be completed sooner.
>>>>>
>>>>> *[2] InProgress#: 11*
>>>>>
>>>>> - If you think we *must* include any issues from this list then
>> please
>>>>> reply on this thread. Also would be great to know how much time you
>>>>> think
>>>>> is needed for these issues. Based on that we can take a call which
>> one
>>>>> to
>>>>> target for this release.
>>>>>
>>>>> *[3] Reviewable#: 14*
>>>>>
>>>>> - All the reviewers and authors should try to close these as soon as
>>>>> possible. If you think that any of the PR needs rework or should be
>>>>> postponed to next release then please update the status and fix
>>>> version
>>>>> for
>>>>> those JIRA's as well.
>>>>>
>>>>> After above JIRA's are reviewed by everyone and based on their inputs
>> we
>>>>> can define a cut off date.
>>>>>
>>>>> *Approximate numbers as it can change based on JIRA updates.
>>>>>
>>>>> Thanks,
>>>>> Sorabh
>>>>>
>>>>> [1]:
>>>>>
>>>>>
>>>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20DRILL%20AND%20issuetype%20in%20(standardIssueTypes()%2C%20subTaskIssueTypes())%20AND%20fixVersion%20%3D%201.16.0%20AND%20status%20%3D%20Open%20ORDER%20BY%20assignee%20ASC
>>>>> [2]:
>>>>>
>>>>>
>>>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20DRILL%20AND%20status%20in%20(%22In%20Progress%22)%20AND%20fixVersion%20%3D%201.16.0%20ORDER%20BY%20assignee%20ASC
>>>>> [3]:
>>>>>
>>>>>
>>>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20DRILL%20AND%20status%20in%20(Reviewable)%20AND%20fixVersion%20%3D%201.16.0%20AND%20(labels%20!%3D%20ready-to-commit%20OR%20labels%20is%20EMPTY)%20ORDER%20BY%20assignee%20ASC
>>>>>
>>>>
>>
>>
