The major version change is from a release perspective. The only change to the versioning which OSGi uses is org.apache.sling.api.resource which went from 2.11 to 2.12
Ioan brought up the issue as part of the pull request that the upgrade to jdk 8 is a significant change. If someone is running sling on a jdk 7 environment then this release will be broken for them. I looked around at other Apache projects and there seems to be a trend that upgrades to JRE support results in a major release upgrade. This would also allow support, if there was ever a need, to do a release for the jdk7 version after this release. - Jason On Mon, Jun 4, 2018, at 1:09 AM, Carsten Ziegeler wrote: > Why do we have a major version change? - I think this is sending the > wrong signal > > Regards > > Carsten > > > Jason E Bailey wrote > > Hi, > > > > We solved 3 issues in this release: > > https://issues.apache.org/jira/projects/SLING/versions/12342941 > > > > There are still some outstanding issues: > > https://issues.apache.org/jira/projects/SLING/versions/12343385 > > > > Staging repository: > > https://repository.apache.org/content/repositories/orgapachesling-1911/ > > > > You can use this UNIX script to download the release and verify the > > signatures: > > https://gitbox.apache.org/repos/asf?p=sling-tooling-release.git;a=blob;f=check_staged_release.sh;hb=HEAD > > > > Usage: > > sh check_staged_release.sh 1911 /tmp/sling-staging > > > > Please vote to approve this release: > > > > [ ] +1 Approve the release > > [ ] 0 Don't care > > [ ] -1 Don't release, because ... > > > > This majority vote is open for at least 72 hours. > > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
