You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by Mahadev Konar <ma...@hortonworks.com> on 2012/06/11 08:46:12 UTC
Board Report due on June 13th.
Hi folks,
There is a board report due on June 13th. Can you guys please send me
an update by tomorrow for inclusion?
thanks
mahadev
Re: Board Report due on June 13th.
Posted by Mahadev Konar <ma...@hortonworks.com>.
Thanks Ivan. I checked out the bookkeeper bits and +1'ed the rc. Can
you send me an updated report?
thanks
mahadev
On Mon, Jun 11, 2012 at 9:58 AM, Ivan Kelly <iv...@apache.org> wrote:
> Here's the proposed report for june. The first line of the second
> paragraph could change if another PMC member checked the rc ;)
>
> =============================================================
> BookKeeper status report for June 2012.
>
> Bookkeeper is a distributed, reliable, and high performance logging
> service. The project also includes Hedwig which is a highly scalable
> Pub/Sub service built on top of ZooKeeper and Bookkeeper with strong
> durability guarantees.
>
> Our second release as a sub-project of ZooKeeper, 4.1.0, will be
> released this week. It fixes 102 issues of both BookKeeper and
> Hedwig. New features include JMX instrumentation and a CLI interface
> to Hedwig.
>
> Infrastructure issues:
> There is a minor issue with Jira. One of applications of BookKeeper is
> journaling for the HDFS namenode. There has been cases in which we
> needed to move jiras from one project to the other, but the current
> jira configuration does not allow contributors to move jira
> issues. Interestingly, the hadoop jira configuration does allow such
> moves, but our request to change the Jira configuration for BookKeeper
> so far has not been accepted.
>
> Community building:
> Since the previous release, we have started receiving more
> contributions from developers across different companies, in
> particular Huawei. They have expressed strong interest in the project
> due to its coupling with HDFS. There has been smaller contributions
> and bug reports from Twitter and Hubspot. In general, we have been
> able to grow the community and increase diversity.
>
> Community:
> * 42 subscribers to bookkeeper-dev
> * 48 subscribers to bookkeeper-user
> * 287 issues opened to date, 140 opened since Jan 1, 2012
> * 24 reporters of Jira issues, 14 since Jan 1, 2012
> * 10 patch contributors
>
Re: Board Report due on June 13th.
Posted by Ivan Kelly <iv...@apache.org>.
Updated release info. I set the release date as the 13th, as the files
will need to propagate to mirrors after Sijie releases them tomorrow.
=============================================================
BookKeeper status report for June 2012.
Bookkeeper is a distributed, reliable, and high performance logging
service. The project also includes Hedwig which is a highly scalable
Pub/Sub service built on top of ZooKeeper and Bookkeeper with strong
durability guarantees.
Our second release as a sub-project of ZooKeeper, 4.1.0, was released
on June 13th. It fixes 102 issues of both BookKeeper and Hedwig. New
features include JMX instrumentation and a CLI interface to Hedwig.
Infrastructure issues:
There is a minor issue with Jira. One of applications of BookKeeper is
journaling for the HDFS namenode. There has been cases in which we
needed to move jiras from one project to the other, but the current
jira configuration does not allow contributors to move jira
issues. Interestingly, the hadoop jira configuration does allow such
moves, but our request to change the Jira configuration for BookKeeper
so far has not been accepted.
Community building:
Since the previous release, we have started receiving more
contributions from developers across different companies, in
particular Huawei. They have expressed strong interest in the project
due to its coupling with HDFS. There has been smaller contributions
and bug reports from Twitter and Hubspot. In general, we have been
able to grow the community and increase diversity.
Community:
* 42 subscribers to bookkeeper-dev
* 48 subscribers to bookkeeper-user
* 287 issues opened to date, 140 opened since Jan 1, 2012
* 24 reporters of Jira issues, 14 since Jan 1, 2012
* 10 patch contributors
Re: Board Report due on June 13th.
Posted by Ivan Kelly <iv...@apache.org>.
Here's the proposed report for june. The first line of the second
paragraph could change if another PMC member checked the rc ;)
=============================================================
BookKeeper status report for June 2012.
Bookkeeper is a distributed, reliable, and high performance logging
service. The project also includes Hedwig which is a highly scalable
Pub/Sub service built on top of ZooKeeper and Bookkeeper with strong
durability guarantees.
Our second release as a sub-project of ZooKeeper, 4.1.0, will be
released this week. It fixes 102 issues of both BookKeeper and
Hedwig. New features include JMX instrumentation and a CLI interface
to Hedwig.
Infrastructure issues:
There is a minor issue with Jira. One of applications of BookKeeper is
journaling for the HDFS namenode. There has been cases in which we
needed to move jiras from one project to the other, but the current
jira configuration does not allow contributors to move jira
issues. Interestingly, the hadoop jira configuration does allow such
moves, but our request to change the Jira configuration for BookKeeper
so far has not been accepted.
Community building:
Since the previous release, we have started receiving more
contributions from developers across different companies, in
particular Huawei. They have expressed strong interest in the project
due to its coupling with HDFS. There has been smaller contributions
and bug reports from Twitter and Hubspot. In general, we have been
able to grow the community and increase diversity.
Community:
* 42 subscribers to bookkeeper-dev
* 48 subscribers to bookkeeper-user
* 287 issues opened to date, 140 opened since Jan 1, 2012
* 24 reporters of Jira issues, 14 since Jan 1, 2012
* 10 patch contributors