You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Radu Cotescu <ra...@apache.org> on 2018/03/07 14:19:49 UTC
[VOTE] Release Apache Sling XSS Protection API 2.0.6
Hi,
We solved 1 issue in this release:
https://issues.apache.org/jira/projects/SLING/versions/12342876
Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-1882
You can use this UNIX script to download the release and verify the
signatures:
https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh
Usage:
curl
https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh
| bash -s 1882
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
Re: [VOTE] Release Apache Sling XSS Protection API 2.0.6
Posted by Daniel Klco <dk...@apache.org>.
+1
On Wed, Mar 7, 2018 at 9:19 AM, Radu Cotescu <ra...@apache.org> wrote:
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12342876
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1882
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://raw.githubusercontent.com/apache/sling-tooling-
> release/master/check_staged_release.sh
>
> Usage:
> curl
> https://raw.githubusercontent.com/apache/sling-tooling-
> release/master/check_staged_release.sh
> | bash -s 1882
>
> 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
>
Re: [VOTE] Release Apache Sling XSS Protection API 2.0.6
Posted by Carsten Ziegeler <cz...@apache.org>.
+1
Radu Cotescu wrote
> Hi,
>
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12342876
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1882
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh
>
> Usage:
> curl
> https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_staged_release.sh
> | bash -s 1882
>
> 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
>
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
Re: [VOTE] Release Apache Sling XSS Protection API 2.0.6
Posted by Jason E Bailey <je...@apache.org>.
+1
- Jason
On Thu, Mar 8, 2018, at 12:17 PM, Stefan Seifert wrote:
> +1
RE: [VOTE] Release Apache Sling XSS Protection API 2.0.6
Posted by Stefan Seifert <ss...@pro-vision.de>.
+1
Re: [VOTE] Release Apache Sling XSS Protection API 2.0.6
Posted by Radu Cotescu <ra...@apache.org>.
Hi Olli,
I have no sane explanation as to why there seem to be arbitrary limits for
those methods instead of the min / max values for the corresponding data
types. Nonetheless, we can open another issue and have them corrected.
Cheers,
Radu
On Fri, 9 Mar 2018 at 17:38 Oliver Lietz <ap...@oliverlietz.de> wrote:
> On Wednesday 07 March 2018 14:19:49 Radu Cotescu wrote:
> > Hi,
>
> Hi Radu,
>
> > We solved 1 issue in this release:
> > https://issues.apache.org/jira/projects/SLING/versions/12342876
>
> while looking at the fix for SLING-7476 I stumbled upon those hardcoded
> values
> for min and max, e.g. -2000000000 and 2000000000 (which seem to be
> arbitrary)
> and wondered why we do not use Integer.MIN_VALUE and Integer.MAX_VALUE
> instead. Any reason for this?
>
> Thanks,
> O.
>
Re: [VOTE] Release Apache Sling XSS Protection API 2.0.6
Posted by Oliver Lietz <ap...@oliverlietz.de>.
On Wednesday 07 March 2018 14:19:49 Radu Cotescu wrote:
> Hi,
Hi Radu,
> We solved 1 issue in this release:
> https://issues.apache.org/jira/projects/SLING/versions/12342876
while looking at the fix for SLING-7476 I stumbled upon those hardcoded values
for min and max, e.g. -2000000000 and 2000000000 (which seem to be arbitrary)
and wondered why we do not use Integer.MIN_VALUE and Integer.MAX_VALUE
instead. Any reason for this?
Thanks,
O.
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachesling-1882
>
> You can use this UNIX script to download the release and verify the
> signatures:
> https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_
> staged_release.sh
>
> Usage:
> curl
> https://raw.githubusercontent.com/apache/sling-tooling-release/master/check_
> staged_release.sh
> | bash -s 1882
>
> 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