I posted the following report. If there is anything prominent missing, revisions are permitted.
Note that the s.apache.org list requires a login and will only work for PMC members. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ # Description: Impala is a high-performance distributed SQL engine. ## Issues: The PMC requested that Google, the owners of "IMPALA: Scalable Distributed DeepRL in DMLab-30"[0], add a disclaimer acknowledging that the ASF owns the Impala trademark. Google declined to do so. We engaged with Mark Thomas, ASF's VP, Brand. He suggested we not pursue this further. See [1] for details. 0: https://deepmind.com/blog/impala-scalable-distributed-deeprl-dmlab-30/ 1: https://s.apache.org/impala-deeprl-rm ## Activity: The previous three months had 248 patches to the master branch, while this three-month period had 364. This pattern in the past was usually a result of a slowdown during the US winter holiday months, and I expect that's true of this uptick, as well. Prominent work in the last three months includes: - Decimal support in Kudu tables - End-to-end compression of metadata - Support for LLVM 5 - Support for Hadoop 3 - Support for the ORC format ## Health report: The project remains very active. Statistics pertaining to this are covered above and below: more than 100 commits per month, more than 100 JIRAs resolved per month, four new people added as PMC members or committers. We have continued a release cadence of about once per quarter. ## PMC changes: - Currently 26 PMC members. - New PMC members: - Philip Zeyliger was added to the PMC on Sun Apr 22 2018 - Thomas Marshall was added to the PMC on Sun Feb 04 2018 ## Committer base changes: - Currently 36 committers. - New committers: - Alexandra Rodoni was added as a committer on Fri Apr 06 2018 - Vuk Ercegovac was added as a committer on Tue Apr 03 2018 ## Releases: - 2.12.0 was released on Mon Apr 23 2018 - 3.0 is in preparation ## JIRA activity: - 504 JIRA tickets created in the last 3 months - 408 JIRA tickets closed/resolved in the last 3 months On Tue, Apr 24, 2018 at 3:36 PM, Phil Steitz <pste...@apache.org> wrote: > 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, 16 May 2018 at 10:30 PDT and the > deadline for > submitting your report is 1 full week prior to that (Wed May 9th)! > > Meeting times in other time zones: > > https://timeanddate.com/s/3h00 > > 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 May 9th). > > 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-05-16/Impala > > Cutting and pasting directly from a Wiki is not acceptable due to > formatting > issues. Line lengths should be limited to 77 characters. > > 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. >
