Version 12 (modified by Mark Evenson, 8 years ago) (diff)


Steps to create a release

  1. Create a stabilization branch and update the version number in (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 (remove the '-dev' suffix)
    3. Update the release date in CHANGES
    4. Run the Ant build
    5. Run the Ant 'abcl.clean' target
    6. Run the Lisp build
    7. Commit the working copy to the version tag
    8. Check out the tag and use it to:
      1. Run the Ant '' and 'abcl.source.tar' targets
      2. Unpack the zip and run compilation on the sources extracted
      3. Run the ANSI tests on the build result
      4. Do the same for the .tar archive
  5. Sign (PGP/GPG) the archives
gpg --detach-signature --armor FILE
  1. Upload the archives and their signatures (to
  2. Update the CLiki Common Lisp Implementation page. (easye: I can't seem to update the date for ABCL listed on this page: it seems to be included markup, but I don't understand how to edit it.)
  3. Update the page
  4. Add a blog item to the ABCL-DEV blog
  5. Update the ABCL website
  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