@@ -7,7 +7,7 @@ should be a three-digit dot-separated version, eventually followed by a
7
7
pre-release string: ``1.2.0 ``, ``1.2.1 ``, ``1.2-dev0 ``, ``1.2.0-beta1 `` are
8
8
valid version numbers.
9
9
10
- In order to release the package you will accounts on Github and PGXN
10
+ In order to release the package you will need accounts on Github and PGXN
11
11
with the right privileges: contact Daniele Varrazzo to obtain them.
12
12
13
13
- Set the right version number in ``META.json `` (note: it's in two different
@@ -21,10 +21,10 @@ with the right privileges: contact Daniele Varrazzo to obtain them.
21
21
- Create a package running ``make package ``. The package will be called
22
22
``dist/pg_repack-$VER.zip ``.
23
23
24
- - Check the packages installs and tests ok with `pgxn client `__::
24
+ - Verify the packages installs and passes tests with `pgxn client `__::
25
25
26
26
pgxn install --sudo -- dist/pg_repack-$VER.zip
27
- pgxn check dist/pg_repack-$VER.zip
27
+ pgxn check dist/pg_repack-$VER.zip
28
28
29
29
(note that ``check`` may require the Postgres bin directory to be added to
30
30
the path; check the ``install`` log to see where ``pg_repack`` executable
@@ -47,7 +47,7 @@ with the right privileges: contact Daniele Varrazzo to obtain them.
47
47
- Upload the docs by pushing in the repos at
48
48
http://reorg.github.io/pg_repack/. The operations are roughly::
49
49
50
- git clone git@github.com:reorg/reorg.github.com.git
50
+ git clone git@github.com:reorg/reorg.github.com.git
51
51
cd reorg.github.com.git
52
52
git submodule init
53
53
git submodule update
0 commit comments