Fwd: Impala Board Report due for November 2018 - Initial Reminder

[Jim Apple <jb...@cloudera.com>]

I posted the report below. We can make changes for a couple of weeks, so
let me know any clarifications you have.

## Description:

Impala is a high-performance distributed SQL engine.

## Activity:

The previous three months had 350 patches to the master branch, while this
three-month period had 330.

Prominent work in the last three months includes:

 - Support for multiple DISTINCT

 - The first Apache two-dot release (3.0.1) was made; normally we only do
   x.y.0 releases. This was done to fix two security issues.

 - Official CentOS support for developers.

 - A number of changes to make the C++ code have a reduced number of
undefined
   behaviors.

 - Support for Hadoop's connector for Azure's new storage system,
   "Azure Data Lake Storage Gen2".

 - Multiple improvements in resource estimation and resource management.

 - Continued improvements in "local catalog" mode.

 - The addition of builtin JSON parsing functions.

 - Graceful node shutdown (with drain/quiesce).

## Health report:

The project remains healthy and metrics (number of commits, bugs filed, and
mailing list activity) remain healthy.

Four new contributors had patches committed.

## PMC changes:

 - Currently 27 PMC members.
 - Joe McDonnell was added to the PMC on Mon Aug 20 2018

## Committer base changes:

 - Currently 44 committers.
 - Quanlong Huang was added as a committer on Thu Aug 23 2018

## Releases:

 - 3.0.1 was released on Tue Oct 23 2018

## Mailing list activity:

Mailing lists metrics that held steady:

 - user@: 83 emails sent in the past 3 months, 87 in the previous cycle.

Mailing list metrics that changed more:

 - dev@: 205 emails sent in the past 3 months, 299 in the previous cycle.
   There is no obvious immediate cause and this is likely just statistical
   fluctuation.

 - reviews@: 7312 emails sent in the past 3 months, 5638 in the previous
   cycle.

## JIRA activity:

 - 409 JIRA tickets created in the last 3 months

 - 386 JIRA tickets closed/resolved in the last 3 months
send email


---------- Forwarded message ---------
From: Phil Steitz <ps...@apache.org>
Date: Wed, Oct 31, 2018 at 8:35 PM
Subject: Impala Board Report due for November 2018 - Initial Reminder
To: Jim Apple <jb...@apache.org>
Cc: <pr...@impala.apache.org>


This email was sent on behalf of the ASF Board.  It is an initial reminder
to
give you plenty of time to prepare the report.

According to board records, you are listed as the chair of a committee that
is
due to submit a report this month. [1] [2]

The meeting is scheduled for Wed, 21 Nov 2018 at 10:30 PST and the deadline
for
submitting your report is 1 full week prior to that (Wed Nov 14th)!

Meeting times in other time zones:

  https://timeanddate.com/s/3pdg

Please submit your report with sufficient time to allow the board members
to review and digest. Again, the very latest you should submit your report
is 1 full week (7days) prior to the board meeting (Wed Nov 14th).

If you feel that an error has been made, please consult [1] and if there
is still an issue then contact the board directly.

As always, PMC chairs are welcome to attend the board meeting.

Thanks,
The ASF Board

[1] -
https://svn.apache.org/repos/private/committers/board/committee-info.txt
[2] - https://svn.apache.org/repos/private/committers/board/calendar.txt
[3] - https://svn.apache.org/repos/private/committers/board/templates
[4] - https://reporter.apache.org/


Submitting your Report
----------------------

Full details about the process and schedule are in [1]. Details about what a
report should look like can be found at:

  https://www.apache.org/foundation/board/reporting

Reports should be posted using the online agenda tool:

  https://whimsy.apache.org/board/agenda/2018-11-21/Impala

Cutting and pasting directly from a Wiki is not acceptable due to formatting
issues. Line lengths should be limited to 77 characters.  If submitting
using Whimsy please press Reflow before Submit.

Chairs may use the Apache Reporter Service [4] to help them compile and
submit a board report.


Resolutions
-----------

There are several templates for use for various Board resolutions.
They can be found in [3] and you are encouraged to use them. It is
strongly recommended that if you have a resolution before the board,
you are encouraged to attend that board meeting.