Skip to content

Commit 479ace0

Browse files
Update release notes
1 parent 126ca22 commit 479ace0

File tree

2 files changed

+10
-9
lines changed

2 files changed

+10
-9
lines changed

README.rst

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,10 @@
22
Ames Stereo Pipeline (ASP)
33
==========================
44

5-
65
.. image:: https://zenodo.org/badge/DOI/latest.svg
76
:target: https://zenodo.org/badge/latestdoi/714891
87

9-
.. image:: https://zenodo.org/badge/DOI/10.5281/zenodo.7497488.svg
8+
.. image:: https://zenodo.org/badge/DOI/Version%203.2.0.svg
109
:target: https://doi.org/10.5281/zenodo.7497488
1110

1211
.. image:: https://readthedocs.org/projects/stereopipeline/badge/?version=latest

RELEASEGUIDE

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -126,22 +126,22 @@ The resulting release tarballs will go to BinaryBuilder/asp_tarballs.
126126

127127
8.) 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

131131
Push 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'
137137
points to the parent repository.)
138138

139139
If more commits were made and it is desired to apply this tag to a
140140
different 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

146146
9.) Create a new release on GitHub, and upload to it the builds and
147147
the pdf documentation. Use the just-created tag. Do not just rename
@@ -152,7 +152,9 @@ NEWS.txt.
152152
Wait a few minutes for Zenodo to mint a link, then visit the Zenodo
153153
page at https://zenodo.org/badge/latestdoi/714891 (which will always
154154
point 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

157159
One could also create an empty release, with a tag, just to get
158160
the Zenodo link, then check that in, make the tag point to the

0 commit comments

Comments
 (0)