Mailing-List: contact oak-dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: oak-dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of julian.reschke@gmx.de
 designates 213.165.64.22 as permitted sender)
Message-ID: <4FF1D0B1.6030602@gmx.de>
Date: Mon, 02 Jul 2012 18:47:45 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: oak-dev@jackrabbit.apache.org
CC: Jukka Zitting <jukka.zitting@gmail.com>
Subject: Re: Oak 0.3 release plan
References: 
 <CAOFYJNaqTz+KB9yY=-CyebbPpuHWWfecR=2XcysTFUN+8+ooaA@mail.gmail.com>
 <CAOFYJNbH0VXveX2jh0uUbwUxZOe8YOGQSDU0-JYPG9Nu4e8Mxw@mail.gmail.com>
In-Reply-To: 
 <CAOFYJNbH0VXveX2jh0uUbwUxZOe8YOGQSDU0-JYPG9Nu4e8Mxw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 2012-07-02 18:30, Jukka Zitting wrote:
> Hi,
>
> As mentioned in the other thread, we never got around to cutting the
> 0.3 release a month ago, so let's do it now instead of going directly
> to 0.4.
>
> I've now cleared all the open 0.3 issues in Jira and reverted Oak
> trunk back to using the 2.5.0 release of Jackrabbit instead of the
> latest 2.6-SNAPSHOT. We'll switch back to the snapshot (and undo the
> related workarounds I added) once the 0.3 release candidate is cut.
> ...

Hmmm; next time wouldn't it make more sense to cut a new 2.5.* release 
which has all the changes we need from trunk?

Best regards, Julian