Hi Jim,

Thanks for your report! I found it really helpful to read your summary. It 
there a portal showing all the previous reports?


Thanks,
Quanlong


At 2018-01-09 03:58:53, "Jim Apple" <[email protected]> wrote:
>BTW, the report is posted.
>
>On Tue, Jan 2, 2018 at 10:28 AM, Jim Apple <[email protected]> wrote:
>> Moving off private@, there's nothing private about this.
>>
>> The report posting tool isn't working for me. I filed
>> https://issues.apache.org/jira/browse/WHIMSY-170
>>
>> The report I will post when it works again is below. Corrections are
>> welcome. Note that this is a report for a single month since we are in
>> our first 3 months as a TLP.
>>
>> ## Description:
>>
>> Impala is a high-performance distributed SQL engine.
>>
>> ## Issues:
>>
>> There are no special issues the board should be aware of.
>>
>> ## Activity:
>>
>> Notable efforts in December include work on decimal and floating point
>> correctness, test and build infrastructure refactoring, the addition of more
>> debugging and profiling information (and the removal of some less helpful
>> information), perfomance improvements for computing table statistics, support
>> for processors with AVX-512, a variety of fixes to runtime filters, and
>> kerberos handling improvements.
>>
>> ## Health report:
>>
>> The project is healthy. December was a slower month than November, likely due
>> to two US holidays at the end of the month. There were 60 commits, 112 dev@
>> emails, 45 user@ emails, 66 tickets resolved, and 94 tickets opened.
>>
>> ## PMC and committer changes:
>>
>> Greg Rahn was added as a committer on December 12.  The most recent new PMC
>> member was added on 2017-09-27.
>>
>> ## Releases:
>>
>> The release process for 2.11 is underway:
>> https://s.apache.org/impala-2.11-vote-results
>>
>> On Sun, Dec 31, 2017 at 10:20 AM, 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, 17 Jan 2018 at 10:30 PST and the deadline 
>>> for
>>> submitting your report is 1 full week prior to that (Wed Jan 10th)!
>>>
>>> Meeting times in other time zones:
>>>
>>>   https://timeanddate.com/s/3dxd
>>>
>>> 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 Jan 10th).
>>>
>>> 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-01-17/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.

Reply via email to