wiki:ReleaseSteps

Steps to create a release

  1. Create a stabilization branch and update the version number in Version.java (on trunk)
  2. (Minimally) run the ANSI tests and Maxima test suite
  3. Stabilize for 2 weeks, during which:
    1. Changes get committed to trunk and backported to the branch from there. On each backport re-run the ANSI tests and the Maxima test suite
    2. Update CHANGES
    3. Check README for up-to-date-ness
  4. On the day of release:
    1. Check out the branch (fresh check out)
    2. Change the version number in Version.java (remove the '-dev' suffix)
    3. Update the release date/version number in CHANGES, README, doc/manual/abcl.tex, and abcl.rdf
    4. Run the Ant 'abcl.release' target
    5. (deprecated: Run the Lisp build)
    6. Commit the working copy to the version tag
    7. Check out the tag and use it to:
      1. Run the Ant 'abcl.release' target
      2. Unpack the source, running compilation on the sources extracted (otherwise the released binaries will contain a reference to the SVN version)
      3. Run the ANSI tests on the build result
      4. Do the same for the .tar archive
  5. Sign (PGP/GPG) the archives with detached, ASCII encoded signatures
gpg --detach-sign --armor FILE

Within Emacs, epa-dired-do-sign help reduce the chore of retyping the passphase.

  1. Upload the archives and their signatures (svn://ommon-lisp.net/project/armedbear/svn/public_html/releases/m.n.p/)
  2. Cliki. Updating the information contained on http://www.cliki.net/ABCL, and the changes will automatically show up on CLiki Common Lisp Implementation
  3. Update the cl-user.net page with a comment. (Not editable?)
  4. Add a blog item to the ABCL-DEV blog
  5. Update the ABCL website
    1. Update the download links to point to the new releases and checksums
    2. Create release notes
    3. Point the left menu to point to the release notes
  6. Send an update to armedbear-announce@ and armedbear-devel@
  7. Update (or ask for an update) the title of the #lisp FreeNode channel
  8. Close the milestone in Trac
  9. (Optional) create new milestones and versions in Trac
Last modified 5 years ago Last modified on 03/06/13 13:20:38