Geofuse Release Process Checklist

Jump to bottom Edit New page

Vicky Vergara edited this page Nov 9, 2015 · 2 revisions

This page hopefully documents that things that need to get done to make a product release.

TODO: If needed, add missing steps, and add details for how to do each step.

I am putting some comments/links on how I did it for pgRouting

More ideas: https://github.com/postgis/postgis/blob/svn-trunk/HOWTO_RELEASE

Hopefully the release goals have been set and completed

For V1.0.0 that is in master

Create/update the change log for Version 1.0.0 - We have the change log in the documentation.
In Master: Create/update the NEWS - also contains the change log - pgRouting News
In Master: - Create a file name VERSION content: v1.0.0
commit your changes:

git commit -a -m 'added NEWS and VERSION files'

CMakeLists.txt has been updated with the correct version number
Create tag for this release - from the command line

      git checkout master
      git tag -a -m "Create the geoFuse-1.1.0 tag"  geoFuse-1.1.0
      git push --tags

Draft and publish a new release on the Github Release
- This can gives you an idea of what to write: (some prose and I copy/pasted the appropriate part of the news) pgRouting release

For V2.0.0 that is in ..... suppose its in develop

copy the NEWS file and VERSION file in develop

git checkout develop
git checkout master NEWS
git checkout master VERSION
git commit -a -m 'added NEWS and VERSION files'

edit NEWS and VERSION and commit.

vi NEWS
vi VERSION
git commit -a -m 'updated NEWS and VERSION files'

I make a backup branch of develop just in case (sometimes I work at 2am so I might be too sleepy):

git checkout develop
git checkout -b develop-backup

go to master and merge/rebase with develop
- I know a flag --ff is used, I just didn't documented it. (please read the above link)

git checkout master
git merge -ff develop

Create tag for this release

      git checkout master
      git tag -a -m "Create the geoFuse-2.0.0 tag" geoFuse-2.0.0
      git push --tags

Draft and publish a new release on the Github Release
- some prose and copy/pasted the appropriate part of the news)