X-Git-Url: https://git.gag.com/?p=fw%2Faltos;a=blobdiff_plain;f=Releasing;h=fdd681bdf59184f81325495c922a651f05f11302;hp=8627d864da6e107e0f8a8a68a8fff99385182491;hb=350d941a825d0271933de0bfdea82d3af5744c21;hpb=ac12e77e3dffc9e9ddb1578a38b32783ad64e940 diff --git a/Releasing b/Releasing index 8627d864..fdd681bd 100644 --- a/Releasing +++ b/Releasing @@ -6,6 +6,7 @@ These are Bdale's notes on how to do a release. - make sure that doc/altusmetrum.xsl has the right copyright year, and add release to the revision history at the front (release notes will be pulled in automatically) + - do the same for doc/micropeak.xsl - update the version in configure.ac git log > ChangeLog @@ -36,7 +37,8 @@ These are Bdale's notes on how to do a release. - if this is a -1 release, then git-buildpackage --git-no-pristine-tar --git-submodules \ - --git-upstream-branch=branch- + --git-upstream-branch=branch- \ # eg 1.3 + --git-upstream-tag= # eg 1.3.1 pristine-tar commit \ ../build-area/altos_.orig.tar.gz \ branch- @@ -71,7 +73,7 @@ These are Bdale's notes on how to do a release. this pushes fresh documents to the web site sudo debian/rules clean - git push origin master branch- debian + git push origin master branch- debian pristine-tar git push --tags push commits and leave the build tree in an uncluttered state