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 ianboston@gmail.com designates
 74.125.82.50 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=sender:content-type:mime-version:subject:from:in-reply-to:date
         :content-transfer-encoding:message-id:references:to:x-mailer;
        b=IFknmhFXs5KV9XleaNU0ydAkmv68RZYeDyXs3+y7MgX3fXd+6f5PBj8IWuVgfcSX8K
         6T2NJPl1Gpc5eBfz5vYf9yh9k9K9q8SnXxOVGnXS+pcXdDqgvOqUfN5IEUMofeEWfrYS
         Z/4wbHVbjXTVJ6c1u3WMkDwXBYAF2wmlRPJVc=
Sender: Ian Boston <ianboston@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1081)
Subject: Re: Jackrabbit 2.1.2 and 2.0.3 release plans
From: Ian Boston <ieb@tfd.co.uk>
In-Reply-To: <AANLkTimQY5z-J0ExfbP_r_NqOEzU89zavDbBFKGLxc0x@mail.gmail.com>
Date: Fri, 22 Oct 2010 11:24:20 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9A3E323B-1153-47A3-91B5-615EE59BDCF2@tfd.co.uk>
References: <AANLkTimQY5z-J0ExfbP_r_NqOEzU89zavDbBFKGLxc0x@mail.gmail.com>
To: dev@jackrabbit.apache.org

=46rom a purely selfish point of view +1,=20
Jukka big thank you for back-porting these fixes to 2.1, I tired several =
times locally and failed miserably.=20
I am going to try and force a delay of our release so we can depend on =
these.
Thanks
Ian

On 21 Oct 2010, at 10:26, Jukka Zitting wrote:

> Hi,
>=20
> At work we have a need for backporting the JCR-2699 improvements back
> to the 2.1 and 2.0 branches. I'd like to push these changes to our
> maintenance branches and push them out in the 2.1.2 and 2.0.3 patch
> releases. This would be against our preference to avoid other than
> low-risk bugfix changes in patch releases, but I believe the benefits
> of the JCR-2699 improvements outweight the increased risk of
> regressions. The changes are internal to jackrabbit-core, so there
> won't be any deployment impact or potential for
> backwards-compatibility issues.
>=20
> Unless anyone objects, I plan to cut both of these releases early next
> week. See the issue tracker for the other fixes targeted for these
> patch releases, and feel free to tag other (already fixed) issues for
> backporting if you think they should be included.
>=20
> BR,
>=20
> Jukka Zitting