Releasing 2.5.0-rc (tasks)

[cvvergara]

prepare

• jenkins
• make sure pull request are pulled
• update release_notes and NEWS
• make sure merges to release/2.5 are made
• pump up version from 2.5.0-beta to 2.5.0-rc and push release/2.5
• run the script
• change README.md

tools/release-scripts/check-release.sh 2 5 0 2.4.2 release/2.5 -rc > ../release_results.txt

• make pull request to master
• accept pull request when appveyor, travis and jenkins are finished

run the check script:

tools/release-scripts/check-release.sh 2 5 0 2.4.2 master -rc > ../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
mkdir 2.5
cp -r build/doc/html/en 2.5
git add 2.5

• commit users documentation

git commit --no-verify  -m  'Updating users documentation for 2.5.0-rc'

• 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.0-rc'

• do when final release
  • latest documentation is 2.5.0

rm -rf  latest
mkdir latest
cp -r build/doc/html/en latest
git commit --no-verify  -a -m  'Updating the latest links with 2.5.0-rc'

• edit the index file to include Prerelease 2.5-rc
  • commit the change

git commit --no-verify  -a -m  'Updating index to have prerelease 2.5.0-rc'

• push & go to working branch

git push
git checkout master

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

CI Tests

• Travis
• Jenkins
• appVeyor

THE TAG

• create the tag & push it

git tag -a -m "Create v2.5.0-rc tag" v2.5.0-rc
git push origin v2.5.0-rc

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

Breaking change on:
-----------------------

    pgr_edgeDisjointPaths:
        Added path_id, cost and agg_cost columns on the result
        Parameter names changed
        The many version results are the union of the one to one version

New Signatures:
---------------
-    pgr_bdAstar(one to one)

New Proposed functions
---------------

-    pgr_bdAstar(one to many)
-    pgr_bdAstar(many to one)
-    pgr_bdAstar(many to many)
-    pgr_bdAstarCost(one to one)
-    pgr_bdAstarCost(one to many)
-    pgr_bdAstarCost(many to one)
-    pgr_bdAstarCost(many to many)
-    pgr_bdAstarCostMatrix
-    pgr_bdDijkstra(one to many)
-    pgr_bdDijkstra(many to one)
-    pgr_bdDijkstra(many to many)
-    pgr_bdDijkstraCost(one to one)
-    pgr_bdDijkstraCost(one to many)
-    pgr_bdDijkstraCost(many to one)
-    pgr_bdDijkstraCost(many to many)
-    pgr_bdDijkstraCostMatrix
-    pgr_lineGraph
-    pgr_connectedComponents
-    pgr_strongComponents
-    pgr_biconnectedComponents
-    pgr_articulationPoints
-    pgr_bridges

enhancement:
-------------------
    pgr_version is now on SQL language

Deprecated Signatures
----------------------

-    pgr_bdastar - use pgr_bdAstar instead

Renamed Functions
------------------

-    pgr_maxFlowPushRelabel - use pgr_pushRelabel instead
-    pgr_maxFlowEdmondsKarp -use pgr_edmondsKarp instead
-    pgr_maxFlowBoykovKolmogorov - use pgr_boykovKolmogorov instead
-    pgr_maximumCardinalityMatching - use pgr_maxCardinalityMatch instead

Deprecated function

-    pgr_pointToEdgeNode

Announce 2.5.0-rc

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

[cvvergara]

• No files changed before execution.

Verify branch to be master

• Already in branch master

Verify typos

• No typos found by script

Verify release_notes.rst & NEWS

• release_notes.rst section 2.5.0 exists
• release_notes.rst section 2.4.2 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

• 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 4.9

update-alternatives: using /usr/bin/gcc-4.9 to provide /usr/bin/gcc (gcc) in manual mode

• Compilation
• Documentation tests
• Pgtap tests OK

Compiling with 4.6

update-alternatives: using /usr/bin/gcc-4.6 to provide /usr/bin/gcc (gcc) in manual mode

• Compilation
• Documentation tests
• Pgtap tests OK

Compiling with 5

update-alternatives: using /usr/bin/gcc-5 to provide /usr/bin/gcc (gcc) in manual mode

• Compilation
• Documentation tests
• Pgtap tests OK

Compiling with 4.8

update-alternatives: using /usr/bin/gcc-4.8 to provide /usr/bin/gcc (gcc) in manual mode

• Build Users documentation
• Build developers documentation
• Compilation
• Documentation tests
• Pgtap tests OK
• Regenerating Users documentation queries OK
• Build Users documentation OK
• Build developers documentation OK
• completed local builds

checking the signature files dont change

• completed check: OK

Locally run the update tester

bash tools/testers/update-tester.sh

All pgRouting versions to be updated must be installed before calling

Updating from 2.4.2 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.4.2.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.4.2 ->> 2.5.0

Updating from 2.4.1 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.4.1.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.4.1 ->> 2.5.0

Updating from 2.4.0 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.4.0.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.4.0 ->> 2.5.0

Updating from 2.3.1 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.3.1.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.3.1 ->> 2.5.0

Updating from 2.3.0 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.3.0.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.3.0 ->> 2.5.0

Updating from 2.2.4 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.2.4.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.2.4 ->> 2.5.0

Updating from 2.2.3 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.2.3.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.2.3 ->> 2.5.0

Updating from 2.2.2 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.2.2.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.2.2 ->> 2.5.0

Updating from 2.2.1 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.2.1.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.2.1 ->> 2.5.0

Updating from 2.2.0 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.2.0.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.2.0 ->> 2.5.0

Updating from 2.1.0 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.1.0.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.1.0 ->> 2.5.0

Updating from 2.0.0 to 2.5.0

/usr/share/postgresql/9.3/extension/pgrouting--2.0.0.sql found
CREATE EXTENSION
CREATE EXTENSION
ALTER EXTENSION
2.0.0 ->> 2.5.0
Reached end of test, all tests passed

• completed update testing

execute the documentation queries

tools/testers/algorithm-tester.pl -documentation
git status

• No files changed
  End of check