Moving to dev@ since there is nothing private in this report. I posted the report to https://whimsy.apache.org/board/agenda/2018-02-21/Impala. Please let me know if you have any corrections or additions.
## Description: Impala is a high-performance distributed SQL engine. ## Issues: There are no special issues the board should be aware of. ## Activity: The most prominent activity in January was the branching to prepare for a 3.0 release. Version 2.11.0 was also released in January, and a 2.x branch is maintained with the anticipated possible release of versions 2.12.0 and beyond. This branching enabled a number of breaking changes to finally land. Other notable efforts include: * Enhancements to sampled statistics collection * The continuation of long-term efforts around the buffer pool * The continuation of long-term efforts around Kudu's RPC * The enablement of different decimal semantics (for the 3.x branch only) * Improved usage of OpenSSL (both performance and correctness) * The exposure of more system information in the web UI * Multiple improvements to test parallelism performance and correctness ## Health report: The project remains healthy. There were 124 dev@emails, 62 user@ emails, 106 tickets opened and 104 resolved, and three new patch authors. There were 98 commits, which is consistent with the average rate over 2017 of 92 commits per month. ## PMC and committer changes: Tianyi Wang was added as a committer on January 5. Philip Zeyliger was added as a committer on January 9. The most recent new PMC member was added on 2017-09-27. ## Releases: 2.11.0 was released on January 18. On Wed, Jan 24, 2018 at 1:05 PM, Phil Steitz <[email protected]> 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, 21 Feb 2018 at 10:30 PST and the deadline > for > submitting your report is 1 full week prior to that (Wed Feb 14th)! > > Meeting times in other time zones: > > https://timeanddate.com/s/3eez > > 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 Feb 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-02-21/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.
