jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting" <jukka.zitt...@gmail.com>
Subject Jackrabbit 1.0 release plan
Date Thu, 02 Mar 2006 14:10:57 GMT
Hi,

An updated version of the release plan. Unless anyone objects with a
-1 by Sunday this week, I will assume lazy consensus for this release
plan and my role as the release manager. The main changes since the
first draft are an updated issue list and a section about conformance
testing. Can someone from Day (David, Marcel, ?) +1 the conformance
testing plan?

RELEASE GOALS

The goals of releasing Jackrabbit version 1.0 are:

  1) Provide a stable and fully conformant JCR 1.0 implementation
  2) Provide a solid ground for improvements and extensions during the 1.x cycle

The Jackrabbit 1.0 release will be considered stable and functional
enough for production use.

RELEASE CONTENTS

The Jackrabbit version 1.0 release will contain the following components:

  * jackrabbit - the Jackrabbit content repository implementation
  * jackrabbit-commons - a general-purpose JCR utility library
  * jackrabbit-textfilters - a collection of text filters for advanced
full text indexing
  * jackrabbit-jca - a JCA connector for Jackrabbit
  * jcr-server - a WebDAV network layer for the JCR API
  * jcr-rmi - an RMI network layer for the JCR API

The current contrib modules to be included in the release should be
promoted before the 1.0 branch is made.

REMAINING ISSUES

The current Jira roadmap lists the following as open issues for Jackrabbit 1.0:

   [JCR-18]  Multithreading issue with versioning
   [JCR-43]  Restore on node creates same-name-sibling of OPV-Version ...
   [JCR-50]  Persistence data of versioning not cleaned up correctly
   [JCR-134] Unreferenced VersionHistory should be deleted automatically
   [JCR-140] Versioning might no be thread safe
   [JCR-151] Installation guide
   [JCR-156] Review test cases and cross check with 1.0 specification
   [JCR-204] Improve recoverability
   [JCR-215] Code is depends on Log4J directly
   [JCR-272] Removal of versions throws javax.jcr.ReferentialIntegrity...
   [JCR-285] Line-separator differences cause PredefinedNodeTypeTest ...
   [JCR-299] errors in text filters can cause indexing to fail without ...
   [JCR-300] Streamline the JCR-RMI network interfaces
   [JCR-301] Improve the JCR-RMI Value classes
   [JCR-302] Use remote callbacks instead of polling for observation ...
   [JCR-303] Add JCR-RMI documentation to the Jackrabbit web site
   [JCR-313] Allow to configure DB persistence managers through JDNI
   [JCR-319] Improve docs for deployment Models 1 and 2 on Tomcat ...
   [JCR-320] BinaryValue equals fails for two objects with two ...
   [JCR-330] Include the README file in the generated jar files

The only critical issues for 1.0 are JCR-156 and JCR-330, all other
issues will be postponed to 1.1 if they do not meet the release
schedule.

CONFORMANCE TESTING

I'd prefer if the conformance testing of the release was done by Day
to avoid any trouble with the TCK license and the conformance
criteria. This would require someone to run the conformance test suite
and report back with the official reports once I post the release
candidates.

RELEASE SCHEDULE

I will create the 1.0 branch from svn trunk on 2006-03-05. The main
focus on the 1.0 branch is to fix the critical issues and prepare for
the release. Non-critical open issues on the 1.0 roadmap will be
postponed to 1.1 when the 1.0 branch is started.

Once the remaining critical issues are resolved I will make the first
release candidate and continue to the release and approval votes. I
hope to have the release shipping by the end of March.

BR,

Jukka Zitting

--
Yukatan - http://yukatan.fi/ - info@yukatan.fi
Software craftsmanship, JCR consulting, and Java development
Mime
View raw message