@@ -28,7 +28,7 @@ Here are the steps to take to make a release of pgTAP:
2828 ` make NO_PGXS=1 installcheck ` )
2929
3030* If you've made any significant changes while testing versions backward, test
31- them again in forward order (8 .1, 8 .2, 8 .3, etc.) to make sure the changes
31+ them again in forward order (9 .1, 9 .2, 9 .3, etc.) to make sure the changes
3232 didn't break any later versions.
3333
3434* Review the documentation in ` doc/pgtap.mmd ` , and make any necessary changes,
@@ -81,7 +81,7 @@ Here are the steps to take to make a release of pgTAP:
8181
8282* Timestamp the ` Changes ` file. I generate the timestamp like so:
8383
84- perl -MDateTime -e 'print DateTime->now->datetime . "Z"'
84+ perl -MDateTime -e 'print DateTime->now->datetime . "Z\n "'
8585
8686 Paste that into the line with the new version, maybe increment by a minute
8787 to account for the time you'll need to actually do the release.
@@ -94,13 +94,14 @@ Here are the steps to take to make a release of pgTAP:
9494* Package the source and submit to [ PGXN] ( http://manager.pgxn.org/ ) .
9595
9696 gem install pgxn_utils
97- git archive --format zip --prefix=pgtap-0.98 .0/ \
98- --output pgtap-0.98 .0.zip master
97+ git archive --format zip --prefix=pgtap-1.0 .0/ \
98+ --output pgtap-1.0 .0.zip master
9999
100100* Push all the changes to GitHub.
101101
102102 git push
103103 git push --tags
104+ git push origin up/gh-pages:gh-pages
104105
105106* Increment the minor version to kick off development for the next release.
106107 The version should be added to the ` Changes ` file, and incremented in the
@@ -114,7 +115,7 @@ Here are the steps to take to make a release of pgTAP:
114115
115116* Commit that change and push it.
116117
117- git ci -m 'Increment to v0.98 .1.'
118+ git ci -m 'Increment to v1.0 .1.'
118119 git push
119120
120121* Start hacking on the next version!
0 commit comments