hello robert. thanks for finally getting this out of the door!
signatures are validating fine, however i found two issues when starting the sling starter and using the links provided on the starter page - not sure if it only happens on my machine: 1. even after logging in as admin/admin, i cannot open composum (browse content). i always get an error dialog "Console assets not accessible..." with another login dialog, but logging in again only shows the same dialog. i think composum is quite a crucial feature for the starter. 2. the "api documentation" link is still pointing to sling 11 stefan >-----Original Message----- >From: Robert Munteanu <[email protected]> >Sent: Friday, February 25, 2022 5:37 PM >To: [email protected] >Subject: [VOTE] Release Apache Sling Starter 12, Apache Sling Project >Archetype 1.0.6 and associated testing modules, > >Hi, > >We solved 80 issues in these releases (not accounting for duplicates): > > >https://issues.apache.org/jira/browse/SLING/fixforversion/12344080 (57) >https://issues.apache.org/jira/browse/SLING/fixforversion/12348435 (3) >https://issues.apache.org/jira/browse/SLING/fixforversion/12345675 (7) >https://issues.apache.org/jira/browse/SLING/fixforversion/12348357 (6) >https://issues.apache.org/jira/browse/SLING/fixforversion/12348291 (7) > >There is no Jira version for the test-fragment bundle, but I've >included it in the release since we keep the same version for all the >testing projects. > >Staging repository: >https://repository.apache.org/content/repositories/orgapachesling-2604 > >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 2604 /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. > >Thanks, >Robert
