hi nitin
the checks were all ok when running checkout from
https://dist.apache.org/repos/dist/dev/jackrabbit
however, i noticed that the verification of previous releases were executed
from https://dist.apache.org/repos/dist/release/jackrabbit.
is there a particular reason for cutting this one from the 'dev' and not from
the 'release'?
and if not: does it have an implication?
kind regards
angela
________________________________
From: Nitin Gupta <ngu...@apache.org>
Sent: Tuesday, May 19, 2020 11:46 AM
To: oak-dev@jackrabbit.apache.org <oak-dev@jackrabbit.apache.org>
Subject: [VOTE] Release Apache Jackrabbit Oak 1.8.22
A candidate for the Jackrabbit Oak 1.8.22 release is available at:
https://dist.apache.org/repos/dist/dev/jackrabbit/oak/1.8.22/
The release candidate is a zip archive of the sources in:
https://svn.apache.org/repos/asf/jackrabbit/oak/tags/jackrabbit-oak-1.8.22/
The SHA1 checksum of the archive is
482328ad73876b5ee1db0af5b885b0b17463986b.
A staged Maven repository is available for review at:
https://repository.apache.org/
The command for running automated checks against this release candidate is:
# run in SVN checkout of
https://dist.apache.org/repos/dist/dev/jackrabbit
$ sh check-release.sh oak 1.8.22
482328ad73876b5ee1db0af5b885b0b17463986b
Please vote on releasing this package as Apache Jackrabbit Oak 1.8.22.
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 Oak 1.8.22
[ ] -1 Do not release this package because...
Regards,
Nitin
