ASF Release Guidelines

    Use scripts/ which 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 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 numbers)
        • svnmucc -U mv dev/allura/allura-1.3.2.tar.gz release/allura/allura-1.3.2.tar.gz mv dev/allura/allura-1.3.2.tar.gz.asc release/allura/allura-1.3.2.tar.gz.asc mv dev/allura/allura-1.3.2.tar.gz.sha512 release/allura/allura-1.3.2.tar.gz.sha512 -m "Move allura 1.3.2 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
      • On repo, update download link and add news item highlighting new features
      • Update download links: wiki [Home], wikipedia
      • Add release data to the
      • Announce (to dev@allura.a.o and users@allura.a.o and announce@a.o)
      • Remove old release (it is automatically archived) like: (change numbers)
        • svnmucc -U rm allura-1.3.1.tar.gz rm allura-1.3.1.tar.gz.asc rm allura-1.3.1.tar.gz.sha512 -m "Remove allura 1.3.1 release"


    Wiki: Home