@@ -126,22 +126,22 @@ The resulting release tarballs will go to BinaryBuilder/asp_tarballs.
126126
1271278.) Commit and tag the release in the VW and ASP repos. Example:
128128
129- git tag 3.2.0
129+ git tag 3.2.0.1
130130
131131Push the tags to the remote server with:
132132
133- git push origin 3.2.0 # commit to your branch
134- git push god 3.2.0 # commit to main branch
133+ git push origin 3.2.0.1 # commit to your branch
134+ git push god 3.2.0.1 # commit to main branch
135135
136136(Here it is assumed that 'origin' points to your own fork and 'god'
137137points to the parent repository.)
138138
139139If more commits were made and it is desired to apply this tag to a
140140different commit, first remove the exiting tag with:
141141
142- git tag -d 3 .2.0
143- git push origin :refs/tags/3 .2.0
144- git push god :refs/tags/3 .2.0
142+ git tag -d v3 .2.0
143+ git push origin :refs/tags/v3 .2.0
144+ git push god :refs/tags/v3 .2.0
145145
1461469.) Create a new release on GitHub, and upload to it the builds and
147147the pdf documentation. Use the just-created tag. Do not just rename
@@ -152,7 +152,9 @@ NEWS.txt.
152152Wait a few minutes for Zenodo to mint a link, then visit the Zenodo
153153page at https://zenodo.org/badge/latestdoi/714891 (which will always
154154point to the 'latest' DOI) and find there this release's URL and put
155- it in README.rst.
155+ it at the top of README.rst, in the appropriate ``target`` field.
156+ Increment the version in the ``image`` field right above that.
157+ Push this update.
156158
157159One could also create an empty release, with a tag, just to get
158160the Zenodo link, then check that in, make the tag point to the
0 commit comments