@@ -28,7 +28,7 @@ Here are the steps to take to make a release of pgTAP:
28
28
` make NO_PGXS=1 installcheck ` )
29
29
30
30
* 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
32
32
didn't break any later versions.
33
33
34
34
* 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:
81
81
82
82
* Timestamp the ` Changes ` file. I generate the timestamp like so:
83
83
84
- perl -MDateTime -e 'print DateTime->now->datetime . "Z"'
84
+ perl -MDateTime -e 'print DateTime->now->datetime . "Z\n "'
85
85
86
86
Paste that into the line with the new version, maybe increment by a minute
87
87
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:
94
94
* Package the source and submit to [ PGXN] ( http://manager.pgxn.org/ ) .
95
95
96
96
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
99
99
100
100
* Push all the changes to GitHub.
101
101
102
102
git push
103
103
git push --tags
104
+ git push origin up/gh-pages:gh-pages
104
105
105
106
* Increment the minor version to kick off development for the next release.
106
107
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:
114
115
115
116
* Commit that change and push it.
116
117
117
- git ci -m 'Increment to v0.98 .1.'
118
+ git ci -m 'Increment to v1.0 .1.'
118
119
git push
119
120
120
121
* Start hacking on the next version!
0 commit comments