Hi, I "improved" the check-release.sh in [2] to work with for the filevault-plugin I'm not too proud on the code, but I needed some workarounds for the differences to the jackrabbit main project. I tested it with the recent plugin and jackrabbit 2.15.17 release - they still pass :-)
If you want to retest the plugin release, you can use: $ sh check-release.sh filevault-plugin 1.0.0 dc660e6bea0654a53ccc77a88fe4677e2399f925 Regards, toby ps: is there a viewvc in dist installed? [2] https://dist.apache.org/repos/dist/dev/jackrabbit/check-release.sh?r=22663 On 24 October 2017 at 18:25:39, Robert Munteanu ([email protected]<mailto:[email protected]>) wrote: On Tue, 2017-10-24 at 07:48 +0000, Tobias Bocanegra wrote: > [ ] +1 Release this package as Apache Jackrabbit Filevault Package > Maven Plugin 1.0.0 +1 Note - the check_release.sh does not seem to be updated so I manually performed the following tests: - builds - signature check - checksums - checking diff between tag and source release artifact Something which should be improved is what we did with OAK-6650/JCR- 4182 and properly suffix the .sha checksum to disambiguate - currently using SHA-1. But by my reading of [1] there is no reason to block the release for it. Robert [1]: http://www.apache.org/dev/release-distribution#sigs-and-sums
