Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (nike.apache.org: domain of jukka.zitting@gmail.com
 designates 209.85.218.165 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type
         :content-transfer-encoding;
        b=fHB4pX4adW025FhMUKKuC9RGq35qWX65rCyap3zNDitW7C0TRL8iL0AuNONhuIIxGp
         Kxh/nS/GUxOlwx6/CQ1BK/a7aKTQUCkAvGD8jFaWR5qa8HOexTiPbFBXHiAGo9WJHmrl
         eif0idEYRRtRzQ8QC9huSyBzItvBOlWQON3U0=
MIME-Version: 1.0
From: Jukka Zitting <jukka.zitting@gmail.com>
Date: Tue, 21 Apr 2009 17:39:14 +0200
Message-ID: <510143ac0904210839x4290df14y11f9964541c76440@mail.gmail.com>
Subject: Jackrabbit 2.0 release plan
To: Jackrabbit Developers <dev@jackrabbit.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Hi,

As a followup to the Jackrabbit 1.6 release plan I sent earlier,
here's a quick roadmap towards Jackrabbit 2.0.

Once the 1.x branch has been created on April 30th, we will upgrade
the JCR dependency in trunk to the JCR 2.0 jar included in the  JSR
283 proposed final draft. This will replace all the
org.apache.jackrabbit.api.jsr283 extension interfaces we currently
have in jackrabbit-api.

At the same point we will also upgrade the required runtime platform
to Java 5. This means that all Java 5 language and library features
will then be available in Jackrabbit trunk.

The 2.0 release also gives us a changes to drop deprecated features
and introduce configuration and other backwards-incompatible changes
that we normally wouldn't do in a minor release. However, any such
change must come with a clear explanation in the 2.0 release notes.

It can be expected that the trunk may be fairly unstable in May as a
result of the JCR 2.0 upgrade and other changes. If you're using the
Jackrabbit trunk for anything else than development or testing, it's
probably a good idea to follow the 1.x branch instead until the JCR
2.0 work has stabilized.

The JSR 283 RI and TCK will be branched off from the Jackrabbit trunk
at some point after both codebases have reached reasonable
feature-completeness. After that, once the JSR 283 is final, we will
upgrade the JCR 2.0 API dependency from the proposed final draft to
the final version and focus on stabilizing the trunk for the
Jackrabbit 2.0 release. I'll keep you posted as more details of these
milestones and expected schedules become available.

BR,

Jukka Zitting