Unfortunately, it turns out that there is a bug in the Servlets
Resolver 2.4.16 release - hence, I removed it from the staging.

Please continue voting only taking into account the Testing OSGi Mock
and the Scripting Core releases.

I will call a new vote for the Servlets Resolver when the issue is fixed.

regards,

Karl

On Tue, Dec 5, 2017 at 2:05 PM, Karl Pauls <[email protected]> wrote:
> I would like to call a vote on the following releases,
>
> Apache Sling Testing OSGi Mock 2.3.6
>
> We solved 2 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12341769
>
>
> Apache Sling Scripting Core 2.0.52
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12342242
>
>
> Apache Sling Servlets Resolver 2.4.16
>
> We solved 2 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12341397
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1826/
>
> 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 1826 /tmp/sling-staging
>
> Please vote to approve these releases:
>
>   [ ] +1 Approve the releases
>   [ ]  0 Don't care
>   [ ] -1 Don't release, because ...



-- 
Karl Pauls
[email protected]

Reply via email to