Releasing v.2.5.4 (tasks)

[cvvergara]

Notes:

• This comment will be constantly edited to reflect the actual work done
• I will be pushing directly to main repository on branch:
  release/2.5 in to fix issues related with the release process and the CI

prepare

• set pre-commit to be for release/2.5
• set this issue to be milestone 2.5.4
• make sure pull request are pulled
• test (pgtap) locally for the following compilers & fix issues of the following compilers:
  • 4.8
  • 4.9
  • 5
  • 6
  • 7
  • 8
• update release_notes and NEWS
• make sure merges to release/2.5 are made
• pump up version from 2.5.3 to 2.5.4 and push release/2.5
• run the script

tools/release-scripts/check-release.sh 2 5 4 2.5.3 release/2.5 > ../release_results.txt

• push to release/2.5
• make sure appveyor, travis and jenkins are finished and are OK
  • jenkins
  • travis
  • appveyor

run the check script:

tools/release-scripts/check-release.sh 2 5 4 2.5.3 master > ../release_results.txt

• write in a comment on this issue the results of the check script

make sure CI tests work

• wait until all tests pass on travis, appveyor and jenkins and script finishes

Documentation

• verify locally correct versions
  • users
  • developers
• Copy the User's documentation to the gh-pages

git checkout gh-pages
rm -rf 2.5
cp -r build/doc/html 2.5
git add 2.5

• commit users documentation

git commit --no-verify  -m  'Updating users documentation for 2.5.4'

• Copy the Developer's documentation to the gh-pages

rm -Rf doxy/2.5
cp -r build/doxygen/html doxy/2.5
git add doxy/2.5

• commit developers documentation

git commit --no-verify  -m  'Updating developers documentation for 2.5.4'

• edit the index file to include Release 2.5 (only when is a minor/mayor release)

• push & go to working branch

git push
git checkout release/2.5

• verify latest when final release should be 2.6
• verify users 2.5
• verify developers 2.5

CI Tests

• jenkins
• travis
• appveyor

THE TAG

• create the tag & push it

git tag -a -m "Create v2.5.4 tag" v2.5.4
git push origin v2.5.4

• Edit the tag
• make sure it reads that is a release
  https://github.com/pgRouting/pgrouting/releases/tag/v2.5.4
• verify the links
• Modify the following changes if needed

pgRouting 2.5.4 Release Notes
-------------------------------------------------------------------------------

To see the issues closed by this release see the [Git closed milestone for 2.5.4 ](https://github.com/pgRouting/pgrouting/issues?utf8=%E2%9C%93&q=milestone%3A%22Release%202.5.4%22%20) on Github.

*Bug fixes*

* Fixes server crash on several functions.

  * pgr_floydWarshall
  * pgr_johnson
  * pgr_astar
  * pgr_bdAstar
  * pgr_bdDijstra
  * pgr_alphashape
  * pgr_dijkstraCostMatrix
  * pgr_dijkstra
  * pgr_dijkstraCost
  * pgr_drivingDistance
  * pgr_KSP
  * pgr_dijkstraVia (proposed)
  * pgr_boykovKolmogorov (proposed)
  * pgr_edgeDisjointPaths (proposed)
  * pgr_edmondsKarp (proposed)
  * pgr_maxCardinalityMatch (proposed)
  * pgr_maxFlow (proposed)
  * pgr_withPoints (proposed)
  * pgr_withPointsCost (proposed)
  * pgr_withPointsKSP (proposed)
  * pgr_withPointsDD (proposed)
  * pgr_withPointsCostMatrix (proposed)
  * pgr_contractGraph (experimental)
  * pgr_pushRelabel (experimental)
  * pgr_vrpOneDepot (experimental)
  * pgr_gsoc_vrppdtw (experimental)
  * Fixes for deprecated functions where also applied but not tested

* Removed compilation warning for g++8
* Fixed a fallthrugh on Astar and bdAstar.

Manage milestones

• close this issue
• close 2.5.4 milestone
• 2.5.5 milestone will be created if needed

Announce 2.5.4

• mail to packagers
• mail to:
  • pgrouting users
  • pgrouting dev
• tweet
• facebbook

[cvvergara]

@robe2
I am having problems on this test
http://winnie.postgis.net:1500/job/pgRouting_PGVersionEDB/7777/console
running bootstrap script ... child process exited with exit code 1

[cvvergara]

• No files changed before execution.

Verify branch to be release/2.5

• Already in branch release/2.5

Verify typos

• No typos found by script

Verify release_notes.rst & NEWS

• release_notes.rst section 2.5.4 exists
• release_notes.rst section 2.5.3 exists
• NEWS is up to date

Check version information

• CMakeLists
  • mayor information is OK
  • Check minor information is OK
  • Check patch information is OK
  • Check dev information is OK
• src/common/test/doc-pgr_version.result
  • src/common/test/doc-pgr_version.result
• VERSION
  -[x] VERSION file branch: OK

Checking signature files exist

• sql/sigs/pgrouting--2.5.4.sig
• sql/sigs/pgrouting--2.5.3.sig
• sql/sigs/pgrouting--2.5.2.sig
• sql/sigs/pgrouting--2.5.1.sig
• sql/sigs/pgrouting--2.5.0.sig
• sql/sigs/pgrouting--2.4.2.sig
• sql/sigs/pgrouting--2.4.1.sig
• sql/sigs/pgrouting--2.4.0.sig
• sql/sigs/pgrouting--2.3.2.sig
• sql/sigs/pgrouting--2.3.1.sig
• sql/sigs/pgrouting--2.3.0.sig
• sql/sigs/pgrouting--2.2.4.sig
• sql/sigs/pgrouting--2.2.3.sig
• sql/sigs/pgrouting--2.2.2.sig
• sql/sigs/pgrouting--2.2.1.sig
• sql/sigs/pgrouting--2.2.0.sig
• sql/sigs/pgrouting--2.1.0.sig
• sql/sigs/pgrouting--2.0.1.sig
• sql/sigs/pgrouting--2.0.0.sig

Locally make a clean build as Release

Compiling with 8

Building the library names
.....OK

• Compilation

[robe2]

@robe2
I am having problems on this test
http://winnie.postgis.net:1500/job/pgRouting_PGVersionEDB/7777/console
running bootstrap script ... child process exited with exit code 1

Should be all set now. I think was just a stuck postgres process - showing all blues now - https://winnie.postgis.net:444/view/pgRouting/job/pgRouting_matrix_branch_2_5/

[cvvergara]

@dersvenhesse
FYI: pgRouting 2.5.4 is released