On 26 Jan 2010, at 14:14, Justin Edelson wrote: > Hi, > > On 1/26/10 2:08 AM, Felix Meschberger wrote: >> Hi Justin, >> >> On 25.01.2010 23:51, Justin Edelson wrote: >> >>> Does it make sense to cut a release of the JCR bundles before the JR 2 >>> release is out? >>> >> Our JCR bundles are currently based on JR 1.6, which is still in >> "maintenance mode". >> > Yes, but I imagine that we're going to want to upgrade them to JR 2 soon. At > least that's my desire. So my question was whether or not it made sense to > release, for example, jcr.base 2.0.6 using JR 1.6 before it gets upgraded to > JR 2. This way, folks who want to stay on JR 1.6 will have a stable release > of the bundles to use while trunk is upgraded to JR 2.
I would agree within this, as someone who has a server bundle that is based on the Jackrabbit Sling Server bundle, based on JR16 it took me 2 weeks to migrate it from 1.5 to 1.6 and fix all the problems. I wouldn't want to have to push a release out based on snapshots, it wouldnt send the right message. Ian > > Currently, it looks to me like these are the bundles which should be upgraded > to JR 2: > jcr.contentloader > jcr.base > jcr.jackrabbit.server > jcr.jackrabbit.usermanager > jcr.jackrabbit.accessmanager > jcr.webdav > >> My current approach is to merge our extensions to Jackrabbit to make it >> useable and extensible (to a certain extent) in an OSGi framework to the >> Jackrabbit project. See my work in the Jackrabbit sandbox [1]. >> >> In the end, we will probably still have our Jackrabbit embedding, which >> is 1.6 based and the new Jackrabbit 2 embedding which will be more like >> native Jackrabbit. >> >> > It's not just about the embedded server. There's a reasonable amount of code > (spread across the bundles listed above) which depends upon > o.a.jackrabbit.api.jsr283.security, which doesn't exist anymore. >> Nevertheless, I we have something to release, and if there is a desire >> to have a release, nothing stops us from releasing ;-) >> > I'm actually not in a good position to say whether or not a release is needed > in the above-listed bundles, i.e. if there are significant fixes from the > last release. I just want to be able to upgrade trunk to JR 2 quickly once a > release is cut. > > Justin >> Just my €.02 >> >> Regards >> Felix >> >> [1] >> >> >>> Justin >>> >>> -------- Original Message -------- >>> Subject: [RESULT] [VOTE] Release Apache Jackrabbit 2.0.0 >>> Date: Mon, 25 Jan 2010 23:47:17 +0100 >>> From: Jukka Zitting<[email protected]> >>> Reply-To: [email protected] >>> To: Jackrabbit Developers<[email protected]> >>> >>> >>> >>> Hi, >>> >>> On Wed, Jan 20, 2010 at 6:59 PM, Jukka Zitting<[email protected]> >>> wrote: >>> >>>> Please vote on releasing this package as Apache Jackrabbit 2.0.0. >>>> >>> The vote passes as follows: >>> >>> +1 Claus Köll >>> +1 Jukka Zitting >>> +1 Marcel Reutegger >>> +1 Martijn Hendriks >>> +1 Michael Dürig >>> +1 Sébastien Launay >>> +1 Thomas Müller >>> >>> Thanks, everyone! I'll announce the release tomorrow as soon as all >>> the mirrors have picked it up. >>> >>> BR, >>> >>> Jukka Zitting >>> >>> >>> >> >
