Hi Julian, On Thu, 2017-05-18 at 16:06 +0200, Julian Reschke wrote: > On 2017-05-18 15:57, Robert Munteanu wrote: > > Hi, > > > > On the road to Sling 9, here's a chunk of releases that can happen > > now. > > > > We solved 4 issues in these releases > > > > https://issues.apache.org/jira/browse/SLING/fixforversion/12340324 > > (1) > > https://issues.apache.org/jira/browse/SLING/fixforversion/12338867 > > (1) > > https://issues.apache.org/jira/browse/SLING/fixforversion/12340575 > > (1) > > https://issues.apache.org/jira/browse/SLING/fixforversion/12338544 > > (1) > > > > Staging repository > > > > https://repository.apache.org/content/repositories/orgapachesling-1 > > 724 > > > > You can use this UNIX script to download the release and verify the > > signatures: > > http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh > > > > Usage: > > sh check_staged_release.sh 1724 /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. > > > I'll keep asking... :-) Why does this reference Jackrabbit versions > that > have been EOL'd years ago?
I guess you mean JCR Base, right? I guess that for us there is no need to bump up the version as this only affects compilation and how package imports are calculated by bnd. This allows users of the bundle to decide for themselves which version of Jackrabbit they want to run against. Note that our current launchpad is built on Oak 1.6/Jackrabbit 2.14 . That being said, I'm not against setting a baseline to the oldest stable release of Jackrabbit. Which one is that however? Looking at http://jackrabbit.apache.org/jcr/index.html http://jackrabbit.apache.org/jcr/news-archive.html I only found a reference to 'October 3rd, 2011: End of life of Jackrabbit 1.x' Robert
