Mailing-List: contact commits-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: svn commit: r805740 - /jackrabbit/trunk/RELEASE-NOTES.txt
Date: Wed, 19 Aug 2009 10:36:55 -0000
To: commits@jackrabbit.apache.org
From: jukka@apache.org
Message-Id: <20090819103656.112CD2388852@eris.apache.org>

Author: jukka
Date: Wed Aug 19 10:36:55 2009
New Revision: 805740

URL: http://svn.apache.org/viewvc?rev=805740&view=rev
Log:
JCR-1104: JSR 283 support

Update release notes, we're now feature-complete.

Modified:
    jackrabbit/trunk/RELEASE-NOTES.txt

Modified: jackrabbit/trunk/RELEASE-NOTES.txt
URL: http://svn.apache.org/viewvc/jackrabbit/trunk/RELEASE-NOTES.txt?rev=805740&r1=805739&r2=805740&view=diff
==============================================================================
--- jackrabbit/trunk/RELEASE-NOTES.txt (original)
+++ jackrabbit/trunk/RELEASE-NOTES.txt Wed Aug 19 10:36:55 2009
@@ -1,4 +1,4 @@
-Release Notes -- Apache Jackrabbit -- Version 2.0-alpha8
+Release Notes -- Apache Jackrabbit -- Version 2.0-alpha9
 
 Introduction
 ------------
@@ -20,9 +20,8 @@
 notable changes in this release are:
 
   * Upgrade to JCR 2.0. This Jackrabbit release implements and is based
-    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.
+    on a pre-release version of the JCR 2.0 API. All of the features
+    required by the JSR 283 specification have been implemented.
 
   * 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
@@ -44,59 +43,6 @@
 
     https://issues.apache.org/jira/browse/JCR
 
-JCR 2.0 feature completeness
-----------------------------
-
-The following 43 top level JCR 2.0 implementation issues are being tracked in
-the Jackrabbit issue tracker.
-
-Open (3 issues)
-  [JCR-1590] JSR 283: Locking
-  [JCR-2085] test case (TCK) maintenance for JCR 2.0
-  [JCR-2208] update tests so that both Query.XPATH and Query:SQL are ...
-
-Resolved (40 issues)
-  [JCR-1564] JSR 283 namespace handling
-  [JCR-1565] JSR 283 lifecycle management
-  [JCR-1588] JSR 283: Access Control
-  [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-1608] JSR 283: Workspace Management
-  [JCR-1609] JSR 283: new Property Types
-  [JCR-1712] JSR 283: JCR Names
-  [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-1974] JSR 283: Evaluate Capabilities
-  [JCR-2028] JSR 283: JCR Path
-  [JCR-2053] JSR 283: Shareable nodes support in query
-  [JCR-2056] JSR 283: Binary interfaces
-  [JCR-2058] JSR 283: VersionManager and new versioning methods
-  [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-2062] JSR 283: Repository Compliance
-  [JCR-2074] JSR 283: New Event Types
-  [JCR-2075] JSR 283: Identifier based event filtering
-  [JCR-2076] JSR 283: QOM and SQL2
-  [JCR-2086] JSR 283: Implementation of EventIterator.getDate
-  [JCR-2090] JSR 283: new methods on NodeType
-  [JCR-2091] Searchability settings in PropertyDefinition
-  [JCR-2092] make spi query code compatible with JCR 2.0
-  [JCR-2093] Implement QueryObjectModelFactory.fullTextSearch() in ...
-  [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: Configuration and Baselines
-  [JCR-2198] Text.escapeIllegalJCRChars should be adjusted to match the ...
-  [JCR-2200] Implement Query.getBindVariableNames()
-  [JCR-2201] Implement QueryResult.getSelectorNames()
-  [JCR-2234] changed behavior of javax.jcr.Value get* methods
-
 Release Contents
 ----------------