Skip to content

Commit 3388305

Browse files
committed
ReleaseChecklist: Add "still in progress" warning and make the release page a single point
1 parent 3f437da commit 3388305

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

ReleaseChecklist.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,13 @@
2121
- [ ] Copy the changelog into the release blog post.
2222

2323
### 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``).
2729
- [ ] 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.
2931
- [ ] Wait for the CI runs on the tag itself.
3032

3133
### Upload Release Artifacts and Publish Binaries
@@ -62,6 +64,7 @@
6264
### Post-release
6365
- [ ] Make sure the documentation for the new release has been published successfully.
6466
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.
6568
- [ ] Publish the blog posts.
6669
- [ ] Create a commit to increase the version number on ``develop`` in ``CMakeLists.txt`` and add a new skeleton changelog entry.
6770
- [ ] Announce on Twitter, including links to the release and the blog post.

0 commit comments

Comments
 (0)