Hi,
I just notice that since revision 23033, the check-release.sh now rely
on the "compgen" command, which is a builtin bash command but not
available in basic sh.
Is it intentional ? In which case we should force the use of bash in the
script header.
BTW, what is the good JIRA project to create such an issue related to
the release process ?
Regards,
Cédric
Le 21/11/2017 à 07:23, Julian Reschke a écrit :
A candidate for the Jackrabbit 2.16.0 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/2.16.0/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/tags/jackrabbit-2.16.0/
The SHA1 checksum of the archive is
a29fa617e671fbb91cf8a649c342e5a9f9859f39.
A staged Maven repository is available for review at:
https://repository.apache.org/
The command for running automated checks against this release
candidate is:
$ sh check-release.sh 2.16.0 a29fa617e671fbb91cf8a649c342e5a9f9859f39
Please vote on releasing this package as Apache Jackrabbit 2.16.0.
The vote is open for the next 72 hours and passes if a majority of at
least three +1 Jackrabbit PMC votes are cast.
[ ] +1 Release this package as Apache Jackrabbit 2.16.0
[ ] -1 Do not release this package because...
Best regards, Julian
--
Cédric Damioli
CMS - Java - Open Source
www.ametys.org
