From 95e462a40e9e926d3bcecf33c8b1bb950d103ad2 Mon Sep 17 00:00:00 2001 From: Blottiere Paul Date: Fri, 15 May 2020 23:20:11 +0200 Subject: [PATCH] Add a release chapter --- doc/development.rst | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/doc/development.rst b/doc/development.rst index f91b7ab..550dc12 100644 --- a/doc/development.rst +++ b/doc/development.rst @@ -152,3 +152,29 @@ and with various PostgreSQL/PostGIS releases: .. _`source`: https://github.com/hobu/laz-perf .. _`DockerHub`: https://hub.docker.com/_/postgres .. _`GitHub Actions`: https://github.com/pgpointcloud/pointcloud/actions + +------------------------------------------------------------------------------ +Release +------------------------------------------------------------------------------ + +Steps for releasing a new version of Pointcloud: + +1. Add a new section to the ``NEWS`` file, listing all the changes associated + with the new release. + +2. Change the version number in the ``Version.config`` and + ``pgsql/expected/pointcloud.out`` files. + +3. Update the value of ``UPGRADABLE`` in ``pgsql/Makefile.in``. This variable + defines the versions from which a database can be upgraded to the new + Pointcloud version. + +4. Create a PR with these changes. + +5. When the PR is merged create a tag for the new release and push it to + GitHub: + +.. code-block:: bash + + $ git tag -a vx.y.z -m 'version x.y.z' + $ git push origin vx.y.z