It was changed from 2.1.1 to 2.2.0 in r1714786 (for SLING-5301), but there was a release in between. Therefore the change from 2.2.0 to 2.3.0 for SLING-5665 seems right to me. Konrad
> On 04 Jul 2016, at 09:13, Konrad Windszus <konra...@gmx.de> wrote: > > I changed the package version of org.apache.sling.api.scripting from 2.2.0 to > 2.3.0 in r1739719 for the semantic change in SLING-5665. > Which package was previously at 2.1.1? > Konrad > >> On 04 Jul 2016, at 08:21, Carsten Ziegeler <cziege...@apache.org> wrote: >> >> I think SLING-5665 is a clarification of the javadocs in the API. >> Although the implementation previously was wrong as well, updating the >> minor version for the package seems to be fine. >> I don't understand why the package version has been changed from 2.1.1 >> to 2.3.0 for that change? This should be 2.2.0. >> >> Releasing the whole API as 2.12.0 sounds good to me in that case. >> >> Regards >> Carsten >> >> Oliver Lietz wrote >>> hi all, >>> >>> for getting some major issues fixed I will have to do bigger changes in >>> Scripting Core and would like to create a branch 2.0 for Core therefore and >>> release 2.0.38 before (doing the changes in trunk which should become 2.1). >>> >>> Scripting Core currently depends on Sling API 2.11.1-SNAPSHOT due to >>> SLING-5665, so Sling API needs to be released first. Should API become >>> 2.11.2 >>> or 2.12.0? Also, baseline issues some warnings (excessive version increase) >>> for Sling API right now. >>> >>> Thanks, >>> O. >>> >>> >> >> >> >> -- >> Carsten Ziegeler >> Adobe Research Switzerland >> cziege...@apache.org >
