+1 for TLP after 4.3.0 release.

-Sijie


On Tue, Sep 10, 2013 at 10:00 AM, FPJ <[email protected]> wrote:

> We are not in incubator, but as a subproject, we could consider mirroring
> what happens there. The report of incubator projects should include a
> description of what is missing for graduation. Given that we have gone a
> long way with the project and apparently this is getting traction across
> different companies, it would be good to start thinking about graduation.
> Even if others disagree with me that we should be considering graduation,
> it
> would be good to state what needs to happen so that we finally graduate.
>
> -Flavio
>
> > -----Original Message-----
> > From: Ivan Kelly [mailto:[email protected]]
> > Sent: 10 September 2013 17:45
> > To: [email protected]
> > Subject: Proposed BookKeeper board report
> >
> > See below. I'm currently working on the mentioned RC.
> >
> > <snip>
> > 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.
> >
> > Focus in the last quarter has been on the 4.2.2 release which at the time
> of
> > writing has a release candidate under consideration. 4.2.2 is a mostly a
> bugfix
> > release, though we have also exposed some new administrative
> > functionality.
> >
> > Release 4.3.0 is still being worked on, though scope may be reduced to
> allow
> > for a more regular release cycle.
> >
> > Infrastructure issues:
> > No issues.
> >
> > Community building:
> > The community growth has settled down and there's now a core set of
> > people across 4 companies regularly contributing to the project.
> >
> > Community:
> > 53 subscribers to bookkeeper-dev
> > 66 subscribers to bookkeeper-user
> > 670 issues opened to date, 64 since June 1, 2013
> > 438 issues resolved to date, 40 since June 1, 2013
> > 41 reporters of Jira issues, 9 since June 1, 2013
> > 20 patch contributors, 7 since June 1, 2013 </snip>
>
>

Reply via email to