What to do to release pg_repack

This document is the list of operations to do to release a new pg_repack version. The version number in this document is indicated by $VER: it should be a three-digit dot-separated version, eventually followed by a pre-release string: 1.2.0, 1.2.1, 1.2-dev0, 1.2.0-beta1 are valid version numbers.

In order to release the package you will accounts on Github and PGXN with the right privileges: contact Daniele Varrazzo to obtain them.

  • Set the right version number in META.json (note: it's in two different places).

  • Set the right release_status in META.json: testing or stable.

  • Commit the above metadata changes.

  • Create a tag, signed if possible:

    git tag -a -s ver_$VER
  • Create a package running make package. The package will be called dist/pg_repack-$VER.zip.

  • Check the packages installs and tests ok with pgxn client:

    pgxn install --sudo -- dist/pg_repack-$VER.zip
    pgxn check dist/pg_repack-$VER.zip

    (note that check may require the Postgres bin directory to be added to the path; check the install log to see where pg_repack executable was installed).

  • Push the code changes and tags on github:

    git push
    git push --tags
  • Upload the package on http://manager.pgxn.org/.

  • Check the uploaded package works as expected:

    pgxn install --sudo -- pg_repack
    pgxn check pg_repack
  • Upload the docs by pushing in the repos at http://reorg.github.io/pg_repack/. The operations are roughly:

    git clone git@github.com:reorg/reorg.github.com.git
    cd reorg.github.com.git
    git submodule init
    git submodule update
    git commit -a -m "Docs upload for release $VER"
    git push
  • Check the page http://reorg.github.io/pg_repack/ is right.

  • Announce the package on reorg-general@pgfoundry.org and pgsql-announce@postgresql.org.