Jackrabbit board report draft

[Jukka Zitting <ju...@gmail.com>]

Hi,

See [1] (copy below) for a draft of our September board report. As
usual, comments and changes are welcome.

[1] http://cwiki.apache.org/confluence/display/JCR/Jackrabbit+Status+September+2009

BR,

Jukka Zitting


Apache Jackrabbit is a fully conforming implementation of the Content
Repository for Java Technology API (JCR, specified in JSR 170).

The Apache Jackrabbit project is in good shape. We have no board-level
issues at this time.

o Releases

  The big news this quarter is the release of Jackrabbit 1.6.0:

    * Apache Jackrabbit 1.6.0 on August 11th

  One patch release was made from the 1.5 branch:

    * Apache Jackrabbit 1.5.7 on August 3rd

  We made an internal release of the Jackrabbit parent POM:

    * org.apache.jackrabbit:jackrabbit:3 on June 26th

  We also continued releasing Jackrabbit 2.0 alphas:

    * Apache Jackrabbit 2.0 alpha3 on July 3rd
    * Apache Jackrabbit 2.0 alpha4 on July 14th
    * Apache Jackrabbit 2.0 alpha7 on August 10th
    * Apache Jackrabbit 2.0 alpha8 on August 18th
    * Apache Jackrabbit 2.0 alpha9 on August 26th

o Legal

  We have asked (see LEGAL-50) the legal team to review the terms under
  which we are redistributing the JCR API jar. The purpose of this is to
  complete the legal records, and this issue is not a blocker to our
  current releases.

  Recent legal discussions regarding the contents of the NOTICE files
  (see for example LEGAL-62) suggest that we have been including some
  unnecessary information in our NOTICEs. We will review our NOTICE files
  before the 2.0 release to comply with the consensus on legal-discuss@.

o Community / Development

  Sébastien Launay joined the Jackrabbit team as a committer and PMC member.

  With the 1.6 release our JCR 1.0 work has entered maintenance mode and
  we're focusing on releasing Jackrabbit 2.0 shortly after JCR 2.0 becomes
  available. We reached JCR 2.0 feature-completeness with the 2.0 alpha9
  release, and that release is also being used for the JCR 2.0 RI and
  TCK candidates.

  The main author of the JCROM project, that implements an alternative to
  the Jackrabbit OCM (object content mapping) component, contacted us about
  bringing the JCROM code to Jackrabbit and possibly merging with our
  existing OCM code.

o Infrastructure

  We are now using the Nexus server at repository.apache.org for staging
  and deploying our releases to the Maven repository.

  The monthly Google Analytics reports we set up earlier this year don't
  seem to be reaching the dev@ list anymore. To work around this we're
  now sharing the reports via svn and our web site.