Steps to create a release
- Create a stabilization branch and update the version number in Version.java (on trunk)
- (Minimally) run the ANSI tests and Maxima test suite
- Stabilize for 2 weeks, during which:
- 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
- Update CHANGES
- Check README for up-to-date-ness
- On the day of release:
- Check out the branch (fresh check out)
- Change the version number in Version.java (remove the '-dev' suffix)
- Update the release date/version number in CHANGES, README, doc/manual/abcl.tex, and abcl.rdf
- Branch the tag
svn copy ^/trunk/abcl ^/tags/1.6.1
- Run the Ant 'abcl.release' target
- (deprecated: Run the Lisp build)
- Commit the working copy to the version tag
- Check out the tag and use it to:
- Run the Ant 'abcl.release' target
- Unpack the source, running compilation on the sources extracted (otherwise the released binaries will contain a reference to the SVN version)
- Run the ANSI tests on the build result
- Do the same for the .tar archive
- Sign (PGP/GPG) the archives with detached, ASCII encoded signatures
gpg --default-key YOUR-KEY --detach-sign --armor FILE
- Upload the archives and their signatures (svn://common-lisp.net/project/armedbear/svn/public_html/releases/m.n.p/)
- Cliki. Updating the information contained on http://www.cliki.net/ABCL, and the changes will automatically show up on CLiki Common Lisp Implementation
- Update the cl-user.net page with a comment. (Not editable?)
- Add a blog item to the ABCL-DEV blog
- Update the ABCL website
- Update the download links to point to the new releases and checksums
- Create release notes
- Point the left menu to point to the release notes
- Send an update to armedbear-announce@ and armedbear-devel@
- Update (or ask for an update) the title of the #lisp FreeNode channel
- Close the milestone in Trac
- (Optional) create new milestones and versions in Trac
Last modified 5 years ago
Last modified on 04/28/20 06:59:18