|
21 | 21 | - [ ] Copy the changelog into the release blog post.
|
22 | 22 |
|
23 | 23 | ### Create the Release
|
24 |
| - - [ ] Create Github release page: https://github.com/ethereum/solidity/releases/new |
25 |
| - - [ ] On the release page, select the ``develop`` branch as new target and set tag to the new version (e.g. `v0.8.5`) (make sure you only `SAVE DRAFT` instead of `PUBLISH RELEASE` before the actual release) |
26 |
| - - [ ] Thank voluntary contributors in the Github release page (use ``git shortlog -s -n -e v0.5.3..origin/develop``). |
| 24 | + - [ ] Create a [release on github](https://github.com/ethereum/solidity/releases/new). |
| 25 | + Set the target to the ``develop`` branch and the tag to the new version, e.g. `v0.8.5`. |
| 26 | + Include the following warning: ``**The release is still in progress and the binaries may not yet be available from all sources.**``. |
| 27 | + Don't publish it yet - click the ``Save draft`` button instead. |
| 28 | + - [ ] Thank voluntary contributors in the Github release notes (use ``git shortlog -s -n -e v0.5.3..origin/develop``). |
27 | 29 | - [ ] Check that all tests on the latest commit in ``develop`` are green.
|
28 |
| - - [ ] Click the `PUBLISH RELEASE` button on the release page, creating the tag. |
| 30 | + - [ ] Click the `Publish release` button on the release page, creating the tag. |
29 | 31 | - [ ] Wait for the CI runs on the tag itself.
|
30 | 32 |
|
31 | 33 | ### Upload Release Artifacts and Publish Binaries
|
|
62 | 64 | ### Post-release
|
63 | 65 | - [ ] Make sure the documentation for the new release has been published successfully.
|
64 | 66 | Go to https://readthedocs.org/projects/solidity/ and verify that the new version is listed, works and is marked as default.
|
| 67 | + - [ ] Remove "still in progress" warning from the release notes. |
65 | 68 | - [ ] Publish the blog posts.
|
66 | 69 | - [ ] Create a commit to increase the version number on ``develop`` in ``CMakeLists.txt`` and add a new skeleton changelog entry.
|
67 | 70 | - [ ] Announce on Twitter, including links to the release and the blog post.
|
|
0 commit comments