Release Check-list

There are a number of manual steps involved in making an Open Dylan release and it’s easy to forget one or two. Hopefully we can automate some of these but for now here is a manual check-list.

  1. Let people know you plan to make a release. Use the Gitter channel for this. Because the Dylan community is small there’s no need to make a release branch; people can just be careful what they commit until the release is out.

  2. Test on supported platforms.

    • Do a 3-stage boostrap.

    • Run test suites and try to figure out if anything serious is broken. (This is an art, currently, and we should make all our tests pass.)

    • Do some ad-hoc testing. (Anything specific to mention here?)

  3. Update the version number in the sources

    • In the release-info library

    • In the build/packages/unix/README file

    • In the file

    • Do a git grep for the previous release number, e.g., “2019.1” and see if anything else needs to be updated.

  4. Update version numbers in build/unix/ to the latest stable versions of the relevant software (Clang+LLVM, the Boehm-Demers-Weiser garbage collector, and libunwind). Download the release tarballs.

  5. Update the release notes. Hopefully these have been maintained as changes were made. It may be worth scanning the commit logs or pull requests.

    To determine what to put in the Contributors section of the notes, this command is useful (with obvious modifications):

    git log --format=short --no-merges v2019.1.0..origin/master | grep '^Author: ' | sort | uniq -c | sort -n
  6. Create a draft release

    This step is primarily to create the release tag in the git repo.

    On click the “Draft a release” button and create a release with name similar to “Open Dylan 2019.1”, tag similar to “v2019.1.0”, any description you like, and make sure the “This is a pre-release” box is checked.

    The major version is always the current year, the minor version is a number starting at 1 for the current year, and the patch version starts at 0.

  7. Build the binaries for supported platforms

    On un*x platforms:

    $ cd opendylan
    $ git co v2019.1.0      # the tag you created above
    $ ./build/unix/

    Use the previous release as the bootstrap compiler so that we can be sure that works. If it doesn’t work, then opendylan/README.rst must be updated to indicate which version can be used to bootstrap the compiler.

    Ask Peter Housel to build the Windows release. :-)

  8. Upload the binaries to GitHub

    Edit the release created previously and upload the binaries. After the last binary has been uploaded, uncheck the “This is a pre-release” checkbox and save/publish the release.

  9. Upload binaries to

    The binaries go in /var/www/ abeaumont, cgay, and housel have access currently.

  10. Update other packages

  11. Update the Downloads page.

  12. Write a news item and publish it on

    Copy from the previous one but don’t feel the need to follow the exact same template. Do include the :Date: header as this is how articles get included in the RSS feed.

  13. Announce the release