You are here
Release Checklist
Steps to be followed to produce a new ROOT release are:
- Get the 'green' light from all main developers
- Check that all the Jenkins builds / CDash builds are green
- Verify that no performance regressions exist in the benchmark system
- Update versions in JIRA
- Update the release notes in
README/ReleaseNotes/vXXX/index.md
- Edit release notes patches section
- From the list the versions in JIRA, select the version and then 'release notes'
git commit README/ReleaseNotes/vXXX/index.md
- 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
- Run from the build directory
$ make version
- Tag main ROOT repository
- Update the release notes in
README/ReleaseNotes/vXXX/index.md
again
- edit README/ReleaseNotes/vXXX/index.md; possibly copying from README/ReleaseNotes/empty.md if this is not a patch release
git commit README/ReleaseNotes/vXXX/index.md
- Update to the next development version
- edit build/version_number (odd patch number)
- make version, check in
- Push to github
$ git push origin vX-YY-00-patches
$ git push origin vX-YY-ZZ
- Tag ROOTTEST repository
- Make source tar file and copy to ftp area on root.cern.ch
- 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
- Produce binary tarfiles
- start the procedure root-release-6.12 (or whichever branch) in Jenkins
- tarfiles and other artifacts are copied to final destination
- Install binaries to CVMFS
- 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-release-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 patch release edit reference-guide page to add the new reference guide for the release.
- Announcements
- send mail to the following mailing lists: root-planning@cern.ch, root-dev@cern.ch, roottalk@cern.ch
- write announcement in RootTalk forum news