Report from the Apache Jackrabbit committee [Michael Dürig] (Submitted March 8th 2017)
## Description: 
   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
   maintained. 
   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. 
   
## Issues: 
   There are no issues requiring board attention at this time.
   
## Activity:
   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 4th major release of Jackrabbit Oak (1.6). 

   There is an ongoing effort to stabilise our continuous integration 
   (Jenkins) infrastructure. The deployment of the Jira plug-in resulted
   in further insight and improvements. It also revealed that over 25%
   of the issues are caused by infrastructure problems rather than 
   our project. 

   The PMC is currently evaluating the impact of the recently published
   SHA-1 collisions on our products. 

## 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. 

   Commit activity was moderate to high this quarter with a plunge around
   the Christmas break. 
  
## PMC changes: 
 - Currently 50 PMC members. 
 - Andrei Dulceanu was added to the PMC on Mon Dec 19 2016 
   
## Committer base changes: 
 - Currently 50 committers. 
 - Andrei Dulceanu was added as a committer on Fri Dec 16 2016 
   
## Releases: 
 - Jackrabbit-2.12.6 was released on Tue Dec 06 2016 
 - Jackrabbit-2.13.5 was released on Wed Dec 07 2016 
 - Jackrabbit-2.10.5 was released on Mon Jan 16 2017 
 - Jackrabbit-2.12.6 was released on Tue Dec 06 2016 
 - Jackrabbit-2.13.5 was released on Wed Dec 07 2016 
 - Jackrabbit-2.13.6 was released on Wed Dec 14 2016 
 - Jackrabbit-2.13.7 was released on Mon Dec 19 2016 
 - Jackrabbit-2.14.0 was released on Tue Jan 03 2017 
 - Jackrabbit-2.15.0 was released on Mon Jan 09 2017 
 - Jackrabbit-2.4.7 was released on Mon Jan 30 2017 
 - Jackrabbit-2.6.8 was released on Mon Feb 06 2017 
 - Jackrabbit-2.8.4 was released on Mon Jan 23 2017 
 - Jackrabbit-2.8.5 was released on Mon Feb 20 2017 
 - Jackrabbit Oak-1.0.36 was released on Tue Jan 03 2017 
 - Jackrabbit Oak-1.0.37 was released on Mon Feb 13 2017 
 - Jackrabbit Oak-1.2.22 was released on Mon Dec 12 2016 
 - Jackrabbit Oak-1.2.23 was released on Tue Jan 10 2017 
 - Jackrabbit Oak-1.4.11 was released on Mon Dec 12 2016 
 - Jackrabbit Oak-1.4.12 was released on Tue Jan 10 2017 
 - Jackrabbit Oak-1.4.13 was released on Tue Feb 07 2017 
 - Jackrabbit Oak-1.5.15 was released on Thu Dec 08 2016 
 - Jackrabbit Oak-1.5.16 was released on Mon Dec 19 2016 
 - Jackrabbit Oak-1.5.17 was released on Wed Jan 04 2017 
 - Jackrabbit Oak-1.5.18 was released on Wed Jan 18 2017 
 - Jackrabbit Oak-1.6.0 was released on Mon Jan 23 2017    
   
## JIRA activity: 
 - 715 JIRA tickets created in the last 3 months 
 - 632 JIRA tickets closed/resolved in the last 3 months 

Board Report March 2017 (last edited 2017-03-08 12:25:41 by MichaelDürig)