##// END OF EJS Templates
add info to sign releases
Matthias Bussonnier -
Show More
@@ -215,20 +215,26 b' We encourage creating a test build of the docs as well.'
215
215
216 Commit the changes to release.py::
216 Commit the changes to release.py::
217
217
218 git commit -am "release $VERSION"
218 git commit -am "release $VERSION" -S
219 git push origin $BRANCH
219 git push origin $BRANCH
220
220
221 (omit the ``-S`` if you are no signing the package)
222
221 Create and push the tag::
223 Create and push the tag::
222
224
223 git tag -am "release $VERSION" "$VERSION"
225 git tag -am "release $VERSION" "$VERSION" -S
224 git push origin $VERSION
226 git push origin $VERSION
225
227
228 (omit the ``-S`` if you are no signing the package)
229
226 Update release.py back to ``x.y-dev`` or ``x.y-maint``, and re-add the
230 Update release.py back to ``x.y-dev`` or ``x.y-maint``, and re-add the
227 ``development`` entry in ``docs/source/whatsnew/index.rst`` and push::
231 ``development`` entry in ``docs/source/whatsnew/index.rst`` and push::
228
232
229 git commit -am "back to development"
233 git commit -am "back to development" -S
230 git push origin $BRANCH
234 git push origin $BRANCH
231
235
236 (omit the ``-S`` if you are no signing the package)
237
232 Now checkout the tag we just made::
238 Now checkout the tag we just made::
233
239
234 git checkout $VERSION
240 git checkout $VERSION
General Comments 0
You need to be logged in to leave comments. Login now