Every PPMC member should read the below docs at least once, several times, because eventually, after graduation, the NetBeans PMC members will be responsible to verify and ensure releases are done in compliance with these rules:
After reading the above, some specific steps and details and examples below.
-decide version of the product, $VERSION (e.g. 9.0-beta, 9.0, etc.)
-press "Build with Parameters", fill $VERSION into the VERSION input line, press Build
-wait for the build to finish
-click on the build that was started above,
-download the build artifacts
-check the MD5 and SHA1 sums of each zip ($ZIP):
md5sum --check $ZIP.md5
sha1sum --check $ZIP.sha1
for ZIP in *.zip; do md5sum --check $ZIP.md5; sha1sum --check $ZIP.sha1; done
(should print things like "<zip>: OK")
-create a GPG key, see:
-for each zip file ($ZIP) do:
gpg --armor --output $ZIP.asc --detach-sig $ZIP
for ZIP in *.zip; do gpg --armor --output $ZIP.asc --detach-sig $ZIP; done
-verify the signatures:
gpg --verify $ZIP.asc $ZIP
for ZIP in *.zip; do gpg --verify $ZIP.asc $ZIP; done
-in a directory (marked as $RELEASE in the following) do:
--setup (this can be reused in the future):
---mkdir -p dev/incubator/netbeans
---svn checkout https://dist.apache.org/repos/dist/dev/incubator/netbeans .
--publishing to staging repository:
---create directories for the release, e.g. incubating-netbeans-platform/incubating-$VERSION, incubating-netbeans-java/incubating-$VERSION
---place the source zips, convenience binaries and the sha1, md5 asn asc files into the appropriate folder, e.g.:
---svn add all the files, e.g.: "svn add incubating-netbeans-java/ incubating-netbeans-platform/"
---commit the files into the staging area:
svn --username "<your-apache-username>" commit
commit message could be something like: "Apache NetBeans 9.0-beta RC1."
It may be possible to skip the --username "<your-apache-username>", but it shouldn't hurt. You'll be asked for a password.
-let CANDIDATE be "rc1", "rc2", etc. depending on which candidate this is
-determine the git revision that was used to build the release - go to the Jenkins job, and look for a long hash after "Revision:". Will be referred to as $HASH.
-prepare a commit message - could be something like "$CANDIDATE of $VERSION release", or something more descriptive. ($COMMIT)
-do the tag:
git tag -a '$VERSION-$CANDIDATE' -m "$COMMIT" $HASH
-push the tag:
git push origin '$VERSION-$CANDIDATE'
(assuming the Apache repo is "origin" for you)
To actually release a candidate, move it to the release area. In addition to the staging area, the release area needs to be checked out:
$ cd $RELEASE
$ mkdir -p repos/dist/release/incubator/netbeans
$ cd repos/dist/release/incubator/netbeans
$ svn checkout https://dist.apache.org/repos/dist/release/incubator/netbeans
Then move the candidate to the release area:
$ svn move $RELEASE/repos/dist/dev/incubator/netbeans/<candidate> .
And then commit the move:
$ svn commit -m "<commitmessage>" dev/incubator/netbeans/release/incubator/netbeans/