Apache Helix is a generic cluster management framework used to build
distributed systems and provides automatic partition management, fault
tolerance and elasticity.

Helix has been incubating since 2012-10-14.

We feel that we are ready for graduation and have started the discussion
internally. We need to update the status page with new committers and also
resolve trade mark.Our processes are continuing to improve and adoption is
increasing both inside and outside of LinkedIn.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be aware
of?

- NONE


How has the community developed since the last report?

- Added Kanak Biscuitwala as a committer
- Receiving external contribution in developing JavaScript bindings for
Helix (see https://github.com/sudowork/node-helix-participant)
- Steady activity on the mailing list


How has the project developed since the last report?

- Making progress on 0.7.0, a release that examines and rethinks every
interaction that Helix exposes to increase ease of use. We hope to release
this month.
- Introduced new coding style guidelines, and simplified the code review
process with new scripts
- Increased documentation of the development process on JIRA pages
- Actively populating the developer wiki and increased the amount of
documentation on the project website
- Received a patch integrating Helix with YARN, to automate management of
YARN containers.


Date of last release:

  2013-05-30 (0.6.1-incubating)

When were the last committers or PMC members elected?

- Kanak Biscuitwala (committer) - 2013-09-20


On Thu, Oct 3, 2013 at 2:37 PM, Patrick Hunt <[email protected]> wrote:

> Any update on this? I don't see it on the incubator wiki...
>
> Patrick
>
> On Wed, Oct 2, 2013 at 6:25 PM, kishore g <[email protected]> wrote:
> > Thanks Pat, will submit the report today.
> >
> >
> > On Sat, Sep 28, 2013 at 11:05 AM, Patrick Hunt <[email protected]> wrote:
> >
> >> Just a reminder, your board report is due weds
> >> http://wiki.apache.org/incubator/October2013
> >>
> >> Patrick
> >>
>

Reply via email to