You are here

Release Checklist

Steps to be followed to produce a new ROOT release are:

  1. Get the 'green' light from all main developers
  2. Check that all the Jenkins builds / CDash builds are green
  3. Modify version number and modify all necessary files
    • edit build/version_number (even patch number for releases)
    • if before 6.04: change PROJECT_NUMBER in documentation/doxygen/Doxyfile
    • edit release notes patches section README/ReleaseNotes/VERSION/
    • Run from the build directory $ make version
  4. Update versions in JIRA
  5. Update the release notes in README/ReleaseNotes/vXXX/ with the list of closed JIRA items
  6. Tag main ROOT repository
    • $ git tag -a vX-YY-ZZ
    • $ git push origin vX-YY-ZZ
  7. Make source tar file and copy to ftp area on
    • Run from the build directory $ make distsrc not on a MacOS machine
    • $ scp ../root_vX.YY.ZZ.source.tar.gz sftnight@root:/home/www/root/download
  8. Tag ROOTTEST repository
  9. Produce binary tarfiles
    • start the procedure root-release-6.04 (or whichever branch) in Jenkins
    • tarfiles and other artifacts are copied to final destination
  10. Change the version number again to next development version
    • if before 6.04: change PROJECT_NUMBER in documentation/doxygen/Doxyfile
    • edit build/version_number (odd patch number)
    • make version, check in and push
    • starting 6.04: update README/ReleaseNotes/vXXX/; possibly copying from README/ReleaseNotes/ if this is not a patch release
    • before 6.04: update doc/vXXX/ (also create vXXX in all directories)
  11. Install binaries to AFS [OBSOLETE]
  12. Install binaries to CVMFS
  13. Update the release pages
    • Generate the release notes with the Jenkins procedure called root-releasenotes
    • Update the releases xml with the Jenkins procedure called root-makeReleasesXml
    • Once authenticated, import the releases xml in the site clicking import here (Be reminded: this works for authenticated users only!).
    • Eventually edit the 'highlights' section, which is currently commented, in the generated release page.
    • If this applies, mark the release as Pro or Old and remove the attribute to the one previously holding it. There are radio buttons exposed by Drupal when editing a release's page.
    • If not a path release edit reference-guide page to add the new reference guide for the release.
  14. Announcements
    • send mail to the following mailing lists:,
    • write announcement in RootTalk forum announcements