jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jukka Zitting <jukka.zitt...@gmail.com>
Subject June report for Jackrabbit
Date Thu, 11 Jun 2009 15:07:44 GMT
Hi,

Here's a draft of the Jackrabbit board report for this month. Please
comment if there's something I'm missing or misrepresenting.

<draft>
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

  We made the following releases from the 1.5 branch:

   * Apache Jackrabbit 1.5.4 on April 7th
   * Apache Jackrabbit 1.5.5 on April 28th
   * Apache Jackrabbit 1.5.6 on June 4th

  We also made the first alpha release of the upcoming Jackrabbit 2.0:

   * Apache Jackrabbit 2.0 alpha1 on June 4th

o Legal

  The current Jackrabbit trunk and the 2.0 alpha1 release have a system
  dependency on an early "for review only" version of the JCR 2.0 API jar
  from JSR 283. No major concerns were raised when this case was discussed
  on the legal-discuss@ mailing list.

o Community / Development

  Jackrabbit was present at the ApacheCon EU where we also organized
  a quite successful JCR meetup.

  The CMIS effort that started in the Jackrabbit sandbox has now become
  the Apache Chemistry project in the Incubator. The other podling with
  Jackrabbit as the sponsoring PMC, Apache Sling, is just about to graduate
  into a standalone TLP.

  The JCR 2.0 specification (JSR 283) is expected to become final in a few
  months, as soon as we've completed the required RI and TCK work in Jackrabbit
  trunk. We're producing source-only alpha releases of the 2.0 codebase to
  give people a chance to review all the new features and to better track our
  progress.

  We are also planning to release Jackrabbit 1.6 as the last minor release
  from the 1.x branch that's still based on the JCR 1.0 API.

o Infrastructure

  We are about to start using the Nexus installation at repository.apache.org
  for staging and deploying our releases to the Maven repository.
</draft>

BR,

Jukka Zitting

Mime
View raw message