Skip to content

Latest commit

 

History

History
37 lines (20 loc) · 1.36 KB

RELEASE.md

File metadata and controls

37 lines (20 loc) · 1.36 KB
Raw

Release process

All releases

This document simply outlines the release process:

  1. Ensure you are running on the oldest supported Erlang version

  2. Remove all -dev extension from versions (see below for all files)

  3. Ensure CHANGELOG is updated and add current date

  4. Update "Compatibility and Deprecations" if a new OTP version is supported. If a new vMAJOR.MINOR, replace "master" with "vVERSION" in the "Deprecations" section

  5. If a new vMAJOR.MINOR, create a new branch "vMAJOR.MINOR" and set CANONICAL= in Makefile

  6. Add an entry for the new version to the OTP compatibility table in the "Compatibility and Deprecations" page

  7. Commit changes above with title "Release vVERSION" and generate new tag

  8. Run make clean test to ensure all tests pass from scratch and the CI is green

  9. Recompile an existing project (for example, Ecto) to ensure manifests can be upgraded

  10. Push branch and the new tag

  11. Publish new zips with make zips, upload Precompiled.zip and Docs.zip to GitHub Releases

  12. Add the release to elixir.csv and _data/elixir-versions.yml files in elixir-lang/elixir-lang.github.com

  13. After a new vMAJOR.MINOR, move back to master, bump versions, start new CHANGELOG, add -dev back and commit "Start vMAJOR.MINOR+1"

Places where version is mentioned

  • VERSION
  • CHANGELOG.md
  • lib/elixir/src/elixir.app.src