You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[ ] 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)
24
+
-[ ] On the release page, select the ``develop`` branch as new target and set tag to the new version (e.g. `v0.8.5`)
25
+
(make sure you only `SAVE DRAFT` instead of `PUBLISH RELEASE` before the actual release).
26
+
Include a warning that the release is still in progress and binaries may not yet be available.
25
27
-[ ] Thank voluntary contributors in the Github release page (use ``git shortlog -s -n -e v0.5.3..origin/develop``).
26
28
-[ ] Check that all tests on the latest commit in ``develop`` are green.
27
29
-[ ] Click the `PUBLISH RELEASE` button on the release page, creating the tag.
@@ -61,6 +63,7 @@
61
63
### Post-release
62
64
-[ ] Make sure the documentation for the new release has been published successfully.
63
65
Go to https://readthedocs.org/projects/solidity/ and verify that the new version is listed, works and is marked as default.
66
+
-[ ] Remove "still in progress" warning from the release page.
64
67
-[ ] Publish the blog posts.
65
68
-[ ] Create a commit to increase the version number on ``develop`` in ``CMakeLists.txt`` and add a new skeleton changelog entry.
66
69
-[ ] Announce on Twitter, including links to the release and the blog post.
0 commit comments