Why can't we fix SLING-6350 in Sling API 2.16.2? The effort for cancelling
these releases is higher than just starting a new release just for the API
On Thu, 1 Dec 2016 at 09:31 Konrad Windszus <konra...@gmx.de> wrote:
> Radu, could you have a look at
> https://issues.apache.org/jira/browse/SLING-6350 and the attached patch?
> If that really is an issue I would like to see this fix included in the
> API 2.16.0 release.
> > On 30 Nov 2016, at 17:24, Radu Cotescu <r...@apache.org> wrote:
> > Hi,
> > We solved 5 issues in these releases:
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12338421
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12338710
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12338547
> > https://issues.apache.org/jira/browse/SLING/fixforversion/12338788
> > Staging repository:
> > https://repository.apache.org/content/repositories/orgapachesling-1586/
> > 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 1586 /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.
> > Cheers,
> > Radu