ASF Release Guidelines
There is a newer version of this page. You can find it here.
- Prerequisites for script:
- have PGP keys set up according to https://infra.apache.org/new-committers-guide.html#set-up-security-and-pgp-keys
- verify it shows up on https://people.apache.org/keys/committer/ and https://downloads.apache.org/allura/KEYS Those only get updated daily
- if on mac,
brew install coreutilsand make sure its on your path - have a python virtualenv active (like the Allura one, or at least have
requests gitpython sixinstalled)
- have PGP keys set up according to https://infra.apache.org/new-committers-guide.html#set-up-security-and-pgp-keys
- Use
scripts/asf-release.shwhich builds a proper release and hashes and email template. - When voting on dev@allura, include details of what was tested. E.g.:
- Sums and sigs OK (log below).
- Build from source tarball succeeds and passes tests on [list platforms].
- Extended tests pass on [list platforms].
- RAT build target passes.
- Expanded tarball matches version control tag exactly (diff log below).
- LICENSE and NOTICE assembled according to http://www.apache.org/dev/licensing-howto.html per discussion at [link].
- LICENSE and NOTICE up-to-date, as no dependencies have been added since initial assembly.
- All copyleft dependencies purged as documented at [issue].
- Copyright date in NOTICE is current.
- CHANGES entry is current.
- Issue tracker clean (no open issues for this release).
- After successful vote
- send a [RESULT] [VOTE] email
- move release files from /dev/ to /release/ like: (change number at beginning, run from any dir)
export VER=1.16.0; svnmucc -U https://dist.apache.org/repos/dist/ mv dev/allura/allura-$VER.tar.gz release/allura/allura-$VER.tar.gz mv dev/allura/allura-$VER.tar.gz.asc release/allura/allura-$VER.tar.gz.asc mv dev/allura/allura-$VER.tar.gz.sha512 release/allura/allura-$VER.tar.gz.sha512 -m "Move allura $VER from dev to release"
- make a tracker milestone for the release and move the relevant closed tickets (this search minus any completed after the release) from "unreleased" into the new milestone for the release
- push the git tag
- wait for release to show up on https://dlcdn.apache.org/allura/
- On allura.apache.org repo, update download link and add news item highlighting new features
- Update download links: wiki [Home], wikipedia
- wikipedia page has been removed and restored again, could happen again. See https://en.wikipedia.org/wiki/Wikipedia:Articles_for_deletion/Apache_Allura
- Add release data to the https://reporter.apache.org/addrelease.html?allura
- Announce (to dev@allura.a.o and users@allura.a.o and announce@a.o)
- Remove old release (it is automatically archived) like: (change number at beginning, run from any dir)
export OLDVER=1.15.0; svnmucc -U https://dist.apache.org/repos/dist/release/allura rm allura-$OLDVER.tar.gz rm allura-$OLDVER.tar.gz.asc rm allura-$OLDVER.tar.gz.sha512 -m "Remove allura $OLDVER release"