Bryan Thompson


  • notify developers that we are closing the branch down for a release and wait for the all clear.
  • verify performance against standard benchmarks
  • verify CI builds.


  • Ensure that the code builds and run the test suite.
  • Bump the version in ./Makefile and ./doc/Doxyfile.
  • Update ./CHANGELOG and ./README.
  • Commit.
  • Create a TAG for the release in SVN. The TAG is the immutable snapshot of the code as of the release. The TAG should have the general pattern tags/MAPGRAPH_RELEASE_X_Y_Z.
  • Create a new directory on sourceforge for the release Upload the README into the directory on sourceforge. The README will be displayed at the bottom of the folder listing on sourceforge once you do this and refresh the page view.
  • Generate the release artifact (make release) and upload into the directory on sourceforge. Be sure to click on the "i" icon and specify the necessary metadata for each release file (sourceforge will not update the "release" until you do this). DO NOT RENAME THESE DEPLOYMENT FILES. The names you give to SF are the actual names for the downloaded files....


  • notify developers that the branch is open again.
  • blog it and elsewhere.
  • post the release notes to the sourceforge project news (admin -> features -> news -> submit)
  • send out an email announcement (we maintain a mailing list).


Wiki: Home

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks