+1. Thanks for preparing the report.

Terence

Sent from my iPhone

> On May 31, 2016, at 4:43 PM, Gokul Gunasekaran <[email protected]> wrote:
> 
> Resending since the format was off in the previous mail.
> 
> *******************
> 
> Tephra Incubator Report - June 2016
> 
> Tephra is a system for providing globally consistent transactions on top of
> Apache HBase and other storage engines.
> 
> Tephra has been incubating since 2016-03-07.
> 
> Three most important issues to address in the move towards graduation.
> 
>  i) Complete project setup
>  ii) Regular releases
>  iii) Improve community engagement
> 
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
> of?
> 
>  * Couple of Infra tickets filed in March 2016 to bootstrap Tephra podling
> are still not resolved.
>    i) INFRA-12015 : Creation of JIRA (and importing of existing JIRAs) for
> Tephra
>    ii) INFRA-11448 : Github integration for Tephra
> 
> How has the community developed since the last report?
> 
>  i) Apache Tephra now powers ACID transactions in Apache Phoenix (since
> v4.7.0).
>  ii) We presented Apache Tephra as a part of the Apache Phoenix talk at
> HBaseCon 2016.
>  iii) We also presented a more elaborate version of the above talk at
> PhoenixCon 2016.
>  iv) We are making progress towards setting up of Project page.
> 
> How has the project developed since the last report?
> 
>  i) We had our first release (0.8.0-incubating) since incubation.
>  ii) We have added support for Apache HBase v1.2 in the latest release
> (0.8.0-incubating).
> 
> Date of last release: 2016-05-31
> 
> Who were the the last committers or PMC members elected?
> 
>  None since the May 2016 report
> 
> Signed-off-by:
> 
> [   ] (tephra) Alan Gates
> [   ] (tephra) Andrew Purtell
> [   ] (tephra) Henry Saputra
> [   ] (tephra) James Taylor
> [   ] (tephra) Lars Hofhansl
> 
>> On Tue, May 31, 2016 at 4:26 PM, Gokul Gunasekaran <[email protected]> wrote:
>> 
>> Hi,
>> 
>> I have included the proposed incubator report for the month of June 2016.
>> Let me know if you have any suggestions. I am planning to add it to the
>> wiki tomorrow EOD.
>> 
>> Thanks,
>> Gokul
>> 
>> ************
>> 
>> Tephra Incubator Report - June 2016
>> 
>> Tephra is a system for providing globally consistent transactions on top
>> of Apache HBase and other storage engines.
>> 
>> Tephra has been incubating since 2016-03-07.
>> 
>> Three most important issues to address in the move towards graduation.
>> 
>> 
>>   1.
>> 
>>   Complete project setup
>>   2.
>> 
>>   Regular releases
>>   3.
>> 
>>   Improve community engagement
>> 
>> 
>> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
>> aware of?
>> 
>> 
>>   -
>> 
>>   Couple of Infra tickets filed in March 2016 to bootstrap Tephra
>>   podling are still not resolved.
>>   -
>> 
>>      i) INFRA-12015 : Creation of JIRA (and importing of existing JIRAs)
>>      for Tephra
>>      -
>> 
>>      ii) INFRA-11448 : Github integration for Tephra
>> 
>> 
>> How has the community developed since the last report?
>> 
>> 
>>   1.
>> 
>>   Apache Tephra now powers ACID transactions in Apache Phoenix (since
>>   v4.7.0).
>>   2.
>> 
>>   We presented Apache Tephra as a part of the Apache Phoenix talk at
>>   HBaseCon 2016.
>>   3.
>> 
>>   We also presented a more elaborate version of the above talk at
>>   PhoenixCon 2016.
>>   4.
>> 
>>   We are making progress towards setting up of Project page.
>> 
>> 
>> How has the project developed since the last report?
>> 
>> 
>>   1.
>> 
>>   We had our first release (0.8.0-incubating) since incubation.
>>   2.
>> 
>>   We have added support for Apache HBase v1.2 in the latest release
>>   (0.8.0-incubating).
>> 
>> 
>> Date of last release: 2016-05-31
>> 
>> Who were the the last committers or PMC members elected?
>> 
>> 
>>   -
>> 
>>   None since the May 2016 report
>> 
>> 
>> Signed-off-by:
>> 
>> [   ] (tephra) Alan Gates
>> 
>> [   ] (tephra) Andrew Purtell
>> 
>> [   ] (tephra) Henry Saputra
>> 
>> [   ] (tephra) James Taylor
>> [   ] (tephra) Lars Hofhansl
>> ************
>> 

Reply via email to