hello andreas. please follow for the voting mails the template from [1] - that means include a link to the JIRA version with the issues of this release.
also note that sling normally uses "even-odd" version policy (see [2]), that means this new release should get version 1.0.2. stefan [1] https://sling.apache.org/documentation/development/release-management.html#starting-the-vote [2] https://sling.apache.org/documentation/development/version-policy.html >-----Original Message----- >From: Andreas Schaefer [mailto:[email protected]] >Sent: Saturday, May 4, 2019 8:45 PM >To: dev >Subject: [VOTE] Release Sling Project Archetype 1.0.1 > >Hi > >Well, that was embarrassing when I discovered that my newly released >archetype did not work as expected. > >There were some issues with default parameters (problems with Maven >Archetype Plugin) as well as an issue with embedded bundles. > >All of these issues are fixed and I check with the >‘build.run.and.deploy.test.sh’ script that all test samples do deploy in >Sling 11 successfully and that the merged versions do render (the only ones >that can). > >I updated the Readme.md file to reflect the changes. > >Staging repository: >https://repository.apache.org/content/repositories/orgapachesling-2076/ ><https://repository.apache.org/content/repositories/orgapachesling-2076/> > >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 ><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 2076 /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. > >- Andy
