+1

Carsten

Am 10.08.2021 um 21:20 schrieb Eric Norman:
It looks like we still need two more binding votes for this one.  Please
review and provide a vote if you have the time.

NOTE: I should clarify that this is the second part of a batch of related
releases.  The first part was voted on and approved last week at [1].  The
just released org.apache.sling.scripting.sightly.runtime:1.2.6-1.4.0
artifact can not really be used until the
org.apache.sling.scripting.sightly:1.4.12-1.4.0 artifact (being voted on
here) is also released due to the tight coupling of the
"org.apache.sling.scripting.sightly.render" package between those bundles.

1.
https://lists.apache.org/thread.html/r19360c5cbb68292ebce5b8fa8f4381dd884b48c9eac9c3475cfe7f27%40%3Cdev.sling.apache.org%3E

Thanks in advance,
Eric

On Sat, Aug 7, 2021 at 7:01 PM Eric Norman <[email protected]> wrote:

Hi,

We solved 3 issues in the "Scripting HTL Engine" release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12350437

Changes:

https://github.com/apache/sling-org-apache-sling-scripting-sightly/compare/org.apache.sling.scripting.sightly-1.4.8-1.4.0...org.apache.sling.scripting.sightly-1.4.12-1.4.0


We solved 2 issues in the "Scripting HTL Testing Content" release:
https://issues.apache.org/jira/browse/SLING/fixforversion/12350469

Changes:

https://github.com/apache/sling-org-apache-sling-scripting-sightly-testing-content/compare/org.apache.sling.scripting.sightly.testing-content-1.0.28-1.4.0...org.apache.sling.scripting.sightly.testing-content-1.0.30-1.4.0


Staging repository:
https://repository.apache.org/content/repositories/orgapachesling-2513/

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 2513 /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
[email protected]

Reply via email to