|
2 | 2 |
|
3 | 3 | This document simply outlines the release process:
|
4 | 4 |
|
5 |
| -1) Remove `-dev` extension from VERSION |
| 5 | +1. Remove `-dev` extension from VERSION |
6 | 6 |
|
7 |
| -2) Ensure CHANGELOG is updated and timestamp |
| 7 | +2. Ensure CHANGELOG is updated and timestamp |
8 | 8 |
|
9 |
| -3) Commit changes above with title "Release vVERSION" and generate new tag |
| 9 | +3. Commit changes above with title "Release vVERSION" and generate new tag |
10 | 10 |
|
11 |
| -4) Run `make clean test` to ensure all tests pass from scratch and the CI is green |
| 11 | +4. Run `make clean test` to ensure all tests pass from scratch and the CI is green |
12 | 12 |
|
13 |
| -5) Push master and tags |
| 13 | +5. Push master and tags |
14 | 14 |
|
15 |
| -6) Release new docs with `make release_docs`, move docs to `docs/stable` |
| 15 | +6. Release new docs with `make release_docs`, move docs to `docs/stable` |
16 | 16 |
|
17 |
| -7) Release new zip with `make release_zip`, push new zip to GitHub Releases |
| 17 | +7. Release new zip with `make release_zip`, push new zip to GitHub Releases |
18 | 18 |
|
19 |
| -8) Merge master into stable branch and push it |
| 19 | +8. Merge master into stable branch and push it |
20 | 20 |
|
21 |
| -9) After release, bump versions, add `-dev` back and commit |
| 21 | +9. After release, bump versions, add `-dev` back and commit |
22 | 22 |
|
23 |
| -10) `make release_docs` once again and push it to `elixir-lang.github.com` |
| 23 | +10. `make release_docs` once again and push it to `elixir-lang.org` |
| 24 | + |
| 25 | +11. Also update `release` file in `elixir-lang.org` |
24 | 26 |
|
25 | 27 | ## Places where version is mentioned
|
26 | 28 |
|
|
0 commit comments