On 15 Jul 2010, at 03:09, Justin Edelson wrote: > I say yes. Ian has asked/suggested that we first do a JR 2 release of the > impacted bundles, followed by a JR 2.1 release and then include the JR 2.1 > bundles in Sling 6. > > So the sequence for jackrabbit.server is: > 1) release 2.1.0 (JR 2.0.0) > 2) release 2.1.2 (JR 2.1.0) > 3) release Sling 6 including jackrabbit.server 2.1.2 > > The WebDAV bundle would be similar. In terms of davex, my inclination is to > wait and do a 1.0.0 release of davex with JR 2.1, but I don't feel strongly > about this. > > Ian - have you reconsidered your need for a released JR 2.0.0 server bundle?
Yes, Speaking from a Sakai point of view, if the changes required are small then we wont need a release and will just move on. What is small ? the 1.6 to 2.0 upgrade caused us to pause for about 2 weeks while we made the change, we have several customised bundles including major modifications to the AccessManager. So small is < 2 days work to upgrade. Do you have any feel for how much change there is between 2.0 and 2.1 ? The other way we can do this is I can capture a snapshot at a working revision of Sling and take that. Since almost every revision of Sling is "working" that should not be to hard. Ian > > Justin > > On Jul 14, 2010, at 8:48 PM, "Mike Moulton (JIRA)" <j...@apache.org> wrote: > >> >> [ >> https://issues.apache.org/jira/browse/SLING-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888644#action_12888644 >> ] >> >> Mike Moulton commented on SLING-1531: >> ------------------------------------- >> >> Is this scheduled for inclusion in Sling 6? >> >> I'm running into JCR-2576 that is fixed by Jackrabbit 2.1.0. >> >>> Upgrade to Jackrabbit 2.1 >>> ------------------------- >>> >>> Key: SLING-1531 >>> URL: https://issues.apache.org/jira/browse/SLING-1531 >>> Project: Sling >>> Issue Type: Task >>> Components: JCR >>> Reporter: Justin Edelson >>> >> >> >> -- >> This message is automatically generated by JIRA. >> - >> You can reply to this email to add a comment to the issue online. >>
