Hi guys, I really have to agree with Unico here. We should not make API changes in the stable "branch". These changes create (a lot of) unexpected work for everybody depending on Jackrabbit with their own projects. If we do need API changes we have to branch off 2.10 first in a stable maintenance branch. We can set the trunk to 2.11 with the odd/even scheme, so we still can create tags as we need them while indicating that these tags are not considered stable and indeed the API might still change.
So my proposal is to: - revert the API breaking changes - create the 2.10 branch - set the version in trunk to 2.11 - create a new 2.10.3 tag of the branch in which we can fix the tag naming as well - re-apply the reverted changes to trunk - create a 2.11.0 tag if needed Of course Unico and I can help with doing this. Wdyt? Regards, Bart On Wed, Aug 5, 2015 at 2:45 PM, Unico Hommes <[email protected]> wrote: > I'm also -1 on this release but for a different reason. > > It seems that there are (again) API changes in a maintenance tag [1]. > I've already indicated that I don't agree with this procedure. That > API changes need to be made on a 2.12 branch only. > > 1. Changesets 1694048 and 1693235 > 2. http://article.gmane.org/gmane.comp.apache.jackrabbit.devel/40628 > > > On Wed, Aug 5, 2015 at 2:27 PM, Davide Giannella <[email protected]> wrote: >> On 05/08/2015 10:01, Amit Jain wrote: >>> Hi Davide, >>> >>> 2.10.1 was mistakenly tagged as jackrabbit-2.10.1 and maybe that >>> carried over. >>> >>> Not sure whether its an option here but can't we just rename the tag >>> in svn? >>> >> Theoretically possible by something like >> >> svn mv \ >> https://svn.apache.org/repos/asf/jackrabbit/tags/jackrabbit-2.10.2/ \ >> https://svn.apache.org/repos/asf/jackrabbit/tags/2.10.2/ >> >> If no one object I will be doing it tomorrow after lunch CEST. >> >> Davide >> >> -- Hippo B.V. - Oosteinde 11, 1017 WT Amsterdam Hippo USA, Inc. - 745 Atlantic Ave, Third Floor, Boston, MA 02111 US +1 877 414 4776 (toll free) Europe +31(0)20 522 4466 www.onehippo.com
