Report from the Apache Jackrabbit committee [Michael Dürig] (submitted March 14th 2018)
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 Jackrabbit content
repository is stable, largely feature complete and actively being
Jackrabbit Oak is an effort to implement a scalable and performant
hierarchical content repository as a modern successor to the Apache
Jackrabbit content repository. It is targeted for use as the
foundation of modern world-class web sites and other demanding
content applications. In contrast to its predecessor, Oak does not
implement all optional features from the JSR specifications and it
is not a reference implementation.
There are no issues requiring board attention at this time
Apache Jackrabbit Oak receives most attention nowadays. All
maintenance branches and the unstable development branch are
continuously seeing moderate to high activity.
Apache Jackrabbit itself is mostly in maintenance mode with most of
the work going into bug fixing and tooling. New features are mainly
driven by dependencies from Oak.
This quarter saw the 5th major release of Jackrabbit Oak (1.8). With
Oak 1.8 out the team is currently discussing future topics including
supporting other persistence back ends, adapting to upcoming Java
versions and how to support older Java versions while maintaining
backward compatibility without losing the ability to invent.
A potential security vulnerability was reported to us by the Apache
Security Team on Dec. 25th. See https://s.apache.org/7l6s. After careful
evaluation and consideration with the reporter no exploitable issue was
identified. See https://s.apache.org/R3Ke. Nevertheless the affected code
was improved to avoid a potential future vulnerability through reuse of
that code in another context. See OAK-7119.
## Health report:
The project is healthy with a continuous stream of traffic on all
mailing lists reflecting the activity of the respective component.
There is a wide range of topics being discussed on the dev and user
lists as well as on the various Jira issues.
Turn around on Jira issues is on the lower end this quarter. It is
expected to rise again once feature work on the next release picks up.
## PMC changes:
- Currently 50 PMC members.
- No new PMC members added in the last 3 months
- Last PMC addition was Robert Munteanu on Mon May 22 2017
- Roy T. Fielding resigned and was removed from the PMC on March 6th.
## Committer base changes:
- Currently 50 committers.
- No new committers added in the last 3 months
- Last committer addition was Robert Munteanu on Mon May 22 2017
- Roy T. Fielding resigned and was removed from committers on March 6th.
- Removed orphaned account "alexparvulescu" from committers. This account
belonged to Alex Parvulescu who went through a name change to Alex Deparvu and
whos new account is "stillalex".
- jackrabbit-2.16.1 was released on Tue Feb 06 2018
- jackrabbit-2.17.0 was released on Mon Dec 18 2017
- jackrabbit-2.17.1 was released on Tue Jan 30 2018
- jackrabbit-2.6.10 was released on Mon Mar 05 2018
- jackrabbit-2.8.7 was released on Fri Dec 29 2017
- oak-1.0.40 was released on Fri Jan 05 2018
- oak-1.0.41 was released on Mon Mar 05 2018
- oak-1.2.28 was released on Tue Jan 16 2018
- oak-1.2.29 was released on Mon Mar 12 2018
- oak-1.4.19 was released on Thu Jan 04 2018
- oak-1.4.20 was released on Mon Feb 12 2018
- oak-1.6.10 was released on Mon Mar 05 2018
- oak-1.6.8 was released on Tue Jan 09 2018
- oak-1.6.9 was released on Wed Feb 07 2018
- oak-1.7.14 was released on Wed Dec 20 2017
- oak-1.8.0 was released on Tue Jan 09 2018
- oak-1.8.1 was released on Mon Jan 22 2018
- oak-1.8.2 was released on Tue Feb 06 2018
## JIRA activity:
- 349 JIRA tickets created in the last 3 months
- 337 JIRA tickets closed/resolved in the last 3 months