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 > >
