File tree Expand file tree Collapse file tree 1 file changed +7
-4
lines changed Expand file tree Collapse file tree 1 file changed +7
-4
lines changed Original file line number Diff line number Diff line change @@ -98,7 +98,7 @@ Release steps
98
98
99
99
To make an actual release (once testing is complete), first push the git tag made by the release script:
100
100
101
- - git push origin r12345
101
+ - git push origin release/ r12345
102
102
103
103
This is the key bit, as the Github release will be anchored to this tag.
104
104
@@ -117,16 +117,19 @@ Once created this zip folder should be downloaded and checked that it installs a
117
117
Zenodo
118
118
------
119
119
120
- Once the zip folder has been created it should be uploaded to Zenodo.
120
+ Once the zip folder has been created it should be uploaded to Zenodo prior to sending a release announcement.
121
+ This helps avoid swamping our GitHub bandwidth with user downloads.
121
122
122
- .. note ::
123
- TODO: Work out how we will do this in the future
123
+ - For a pre-release, do not upload to the main MESA zenodo repository.
124
+ Instead upload to its own Zenodo entry. This can be done on a personal account.
125
+ - Official releases need to be uploaded to `this MESA Zenodo page <https://doi.org/10.5281/zenodo.2602941 >`_.
124
126
125
127
Send an email to mesa-users
126
128
---------------------------
127
129
128
130
Send an email announcing the release, this should include:
129
131
132
+ - Link to Zenodo for dowload (not GitHub).
130
133
- A brief summary of the changes
131
134
- A link to the Changelog
132
135
- Highlight any very disruptive changes that might have occurred
You can’t perform that action at this time.
0 commit comments