You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@jackrabbit.apache.org by ju...@apache.org on 2009/06/16 12:52:05 UTC

svn commit: r785157 - /jackrabbit/trunk/RELEASE-NOTES.txt

Author: jukka
Date: Tue Jun 16 10:52:03 2009
New Revision: 785157

URL: http://svn.apache.org/viewvc?rev=785157&view=rev
Log:
Updated release notes in preparation for 2.0-alpha3

Modified:
    jackrabbit/trunk/RELEASE-NOTES.txt

Modified: jackrabbit/trunk/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/RELEASE-NOTES.txt?rev=785157&r1=785156&r2=785157&view=diff
==============================================================================
--- jackrabbit/trunk/RELEASE-NOTES.txt (original)
+++ jackrabbit/trunk/RELEASE-NOTES.txt Tue Jun 16 10:52:03 2009
@@ -1,12 +1,11 @@
-Release Notes -- Apache Jackrabbit -- Version 2.0-alpha1
+Release Notes -- Apache Jackrabbit -- Version 2.0-alpha3
 
 Introduction
 ------------
 
-This is the first alpha release of Apache Jackrabbit 2.0. This release
-implements the Proposed Final Draft (PFD) version of the JCR 2.0 API,
-that is being specified by the Java Specification Request 283 (JSR 283,
-http://jcp.org/en/jsr/detail?id=283).
+This is the second alpha release of Apache Jackrabbit 2.0. This release
+implements a pre-release version of the JCR 2.0 API, specified by the
+Java Specification Request 283 (JSR 283, http://jcp.org/en/jsr/detail?id=283).
 
 The purpose of this alpha release is to allow people to test and review
 the new JCR 2.0 features before they are finalized. Feedback to both the
@@ -21,14 +20,18 @@
 notable changes in this release are:
 
   * Upgrade to JCR 2.0. This Jackrabbit release implements and is based
-    on the PFD version of the JCR 2.0 API. See below for a status listing
-    of the issues related to JCR 2.0 changes. We expect to achieve full
-    feature-completeness in time for the final Jackrabbit 2.0 release.
+    on a pre-release version of the JCR 2.0 API. See below for a status
+    listing of the issues related to JCR 2.0 changes. We expect to achieve
+    full feature-completeness in time for the final Jackrabbit 2.0 release.
 
   * Upgrade to Java 5. All of Jackrabbit (except the jcr-tests component)
     now requires Java 5 as the base platform. Java 1.4 environments are no
     longer supported.
 
+  * Removal of deprecated classes and features. Jackrabbit 2.0 is not
+    backwards compatible with client code that used any classes or features
+    that had been deprecated during the 1.x release cycle.
+
   * Separate JCR Commons components. Many of the general-purpose JCR
     components like JCR-RMI and OCM are now developed and released
     separately from the Jackrabbit content repository. See the individual
@@ -42,49 +45,51 @@
 JCR 2.0 feature completeness
 ----------------------------
 
-The following 36 top level JCR 2.0 implementation issues are being tracked in
+The following 38 top level JCR 2.0 implementation issues are being tracked in
 the Jackrabbit issue tracker. Most of them have already been partially
 implemented, but the issue will only be marked as resolved once no more
 related work is needed.
 
-Open (25 issues)
-  [JCR-1564] JSR 283 namespace handling
+Open (16 issues)
   [JCR-1565] JSR 283 lifecycle management
   [JCR-1588] JSR 283: Access Control
-  [JCR-1589] JSR 283: Retention & Hold Management
   [JCR-1590] JSR 283: Locking
-  [JCR-1591] JSR 283: NodeType Management
-  [JCR-1592] JSR 283: Baselines & Activities
   [JCR-1608] JSR 283: Workspace Management
-  [JCR-1609] JSR 283: new Property Types
   [JCR-1712] JSR 283: JCR Names
-  [JCR-1947] JSR 283: Node Type Attribute Subtyping Rules
   [JCR-1974] JSR 283: Evaluate Capabilities
-  [JCR-2028] JSR 283: JCR Path
-  [JCR-2056] JSR 283: Binary interfaces
   [JCR-2058] JSR 283: VersionManager and new versioning methods
-  [JCR-2060] JSR 283: Access Nodes and Properties by Array of "NameGlob"
-  [JCR-2061] JSR 283: References and Dereferencing of Property Values
   [JCR-2062] JSR 283: Repository Compliance
-  [JCR-2076] JSR 283: Joins
+  [JCR-2076] JSR 283: QOM and SQL2
   [JCR-2085] test case (TCK) maintenance for JCR 2.0
   [JCR-2086] JSR 283: Implementation of EventIterator.getDate
-  [JCR-2091] Searchability settings in PropertyDefinition
   [JCR-2092] make spi query code compatible with JCR 2.0
   [JCR-2116] JSR 283: Built-In Node Types
   [JCR-2117] JSR 283: adopt CND syntax changes
+  [JCR-2137] Use type StaticOperand for fullTextSearchExpression
+  [JCR-2140] JSR 283: Baselines
 
-Resolved (11 issues)
+Resolved (22 issues)
+  [JCR-1564] JSR 283 namespace handling
+  [JCR-1589] JSR 283: Retention & Hold Management
+  [JCR-1591] JSR 283: NodeType Management
+  [JCR-1592] JSR 283: Activities
   [JCR-1593] JSR 283: Simple versioning
+  [JCR-1609] JSR 283: new Property Types
   [JCR-1834] JSR 283: Create RepositoryFactory implementation
   [JCR-1839] JSR 283: Introduce Event.getDate()
   [JCR-1849] JSR 283: EventJournal
   [JCR-1904] JSR 283: Event user data
+  [JCR-1947] JSR 283: Node Type Attribute Subtyping Rules
+  [JCR-2028] JSR 283: JCR Path
   [JCR-2053] JSR 283: Shareable nodes support in query
+  [JCR-2056] JSR 283: Binary interfaces
   [JCR-2059] JSR 283: Access Property/Node from Session
+  [JCR-2060] JSR 283: Access Nodes and Properties by Array of "NameGlob"
+  [JCR-2061] JSR 283: References and Dereferencing of Property Values
   [JCR-2074] JSR 283: New Event Types
   [JCR-2075] JSR 283: Identifier based event filtering
   [JCR-2090] JSR 283: new methods on NodeType
+  [JCR-2091] Searchability settings in PropertyDefinition
   [JCR-2093] Implement QueryObjectModelFactory.fullTextSearch() in ...
 
 Release Contents
@@ -111,3 +116,15 @@
 
 For more information, visit http://jackrabbit.apache.org/
 
+About The Apache Software Foundation
+------------------------------------
+
+Established in 1999, The Apache Software Foundation provides organizational,
+legal, and financial support for more than 100 freely-available,
+collaboratively-developed Open Source projects. The pragmatic Apache License
+enables individual and commercial users to easily deploy Apache software;
+the Foundation's intellectual property framework limits the legal exposure
+of its 2,500+ contributors.
+
+For more information, visit http://www.apache.org/
+