THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
The artifacts that end up in the distribution directory are the source distributions (along with their checksums and signatures), so they need to be copied from the Maven repo to a release candidate directory on apache dist, so the vote can begin:
| No Format |
|---|
VERSION=X.Y.Z RC_NUMBER=n REPOSITORY_ID=xxxx # Should be a number, for example 1013. Find the number in NEXUS staging repository: orgapachebigtop-1013 svn checkout https://dist.apache.org/repos/dist/dev/bigtop bigtop-dist-dev cd bigtop-dist-dev mkdir bigtop-$VERSION-RC1${VERSION}-RC${RC_NUMBER} cd bigtop-$VERSION-RC1${VERSION}-RC${RC_NUMBER} # md5 and sha1 are out-of-date and should not be used, see: http://www.apache.org/dev/release-distribution#sigs-and-sums wget --no-check-certificate https://repository.apache.org/content/repositories/orgapachebigtop-$REPOSITORY${REPOSITORY_ID}/org/apache/bigtop/bigtop/$VERSION${VERSION}/bigtop-$VERSION${VERSION}-project.tar.gz wget --no-check-certificate https://repository.apache.org/content/repositories/orgapachebigtop-$REPOSITORY${REPOSITORY_ID}/org/apache/bigtop/bigtop/$VERSION${VERSION}/bigtop-$VERSION${VERSION}-project.tar.gz.asc # manually generate sha256 and sha512 sha256sum bigtop-$VERSION${VERSION}-project.tar.gz > bigtop-$VERSION${VERSION}-project.tar.gz.sha256 sha512sum bigtop-$VERSION${VERSION}-project.tar.gz > bigtop-$VERSION${VERSION}-project.tar.gz.sha512 cd .. svn add bigtop-$VERSION-RC1${VERSION}-RC${RC_NUMBER} svn ci -m "Apache Bigtop $VERSION-RC1${VERSION}-RC${RC_NUMBER}" |
8. Sanity Check
TODO
- Check the SHA1 checksums
...