|Deletions are marked like this.||Additions are marked like this.|
|Line 2:||Line 2:|
|[REPORT] Apache Jackrabbit (preliminary version)||[REPORT] Apache Jackrabbit (submitted June 11th 2012)|
[REPORT] Apache Jackrabbit (submitted June 11th 2012) The Apache Jackrabbit™ content repository is a fully conforming implementation of the Content Repository for Java™ Technology API (JCR, specified in JSR 170 and 283). The Apache Jackrabbit project is in good shape. We have no board-level issues at this time. o Releases We made the following unstable 2.5.x releases from Jackrabbit trunk. * Apache Jackrabbit 2.5.0 on June 2nd The following patch releases were made from earlier maintenance branches: * Apache Jackrabbit 2.2.12 on April 23rd * Apache Jackrabbit 2.4.1 on April 3rd * Apache Jackrabbit 2.4.2 on June 11th This quarter also saw the first releases from the Jackrabbit Oak subproject: * Apache Jackrabbit Oak 0.2.1 on May 7th * Apache Jackrabbit Oak 0.1 on April 3rd Note, there is no Oak 0.2 release since the release vote failed due to a license header issue. The issue was quickly resolved and the release re-cut into 0.2.1 o Community / Development * Unico Hommes and Christian Stocker joined the Jackrabbit team as committers and PMC members. * Work on Jackrabbit Oak is gaining momentum: there where two Hackathons in the last quarter during which great progress was made. This eventually lead to the releases 0.1. and 0.2.1 as initially planned. Currently we are discussing whether, how and what we want to contribute to the .adaptTo(Berlin) 2012 conference in September. .adaptTo(Berlin) is a technical meet up focused on the technical stack of Apache Sling including Apache Jackrabbit and Apache Felix and is addressed to all developers using this stack or parts of it. Being part of that event would allow us to broaden the community and further spark interest for Apache Jackrabbit Oak. * Alex Parvulescu has successfully taken up the role of a release manager. * There is renewed interest on the OCM codebase, driven by Ard Schrijvers. We expect to be able to cut a new, long overdue OCM release in near future. * ModeShape, a JCR implementation from JBoss, is working with us to improve the JCR test suite. To better facilitate this cooperation we may want to split the test suite away from the main Jackrabbit release schedule. * Jukka Zitting resigned as chairman of the Jackrabbit PMC due to his new role at the Incubator. Michael Dürig was elected and acknowledged as new chairman. o Infrastructure We are still in progress of migrating from Confluence to the new CMS.