Make A Dirac Tag And Release

In Git

• In releases.cfg of the master branch add new version
• in release.notes of the release branch write release notes
• commit changes to the proper branches: The version information is taken from the releases.cfg of the master branch. If we were to change this in the release branch and the merge them into the master and other branches we would always get merge conflicts.
• Make a tag in GIT of the release branch

 git tag -a vXXrYYpZZ -m"Some comment for the tag" [CommitSHA]
 git push origin vXXrYYpZZ

• dirac-distribution -l ILCDIRAC -r [Version]
• Run the last line that is printed by the previous command

You are done! Or nearly. You need to change the pilot version used by DIRAC: in the CS, under /Operations/ilc/ILC-Production/Pilot/Version, you need to change the version to the one you created: TAG (for example).

Once the release is made, you also need to update the file /afs/cern.ch/eng/clic/data/ILCDIRACTars/defaults/ilc.cfg to specify the new release number.

To make sure you pick up the right version straight away, you need to restart the TaskQueueDirector, the SiteDirector=(s) and the =Matcher. This can be done using the dirac-admin-sysadmin-cli tool.

Changing the pilot version needs some time to be effective, as all pilots that were submitted with the old pilot version have to die to empty the queues. So make sure your changes are OK. Running on the DEV system helps of course. The release procedure is identical.

Updating the Code Documentation

New Sphinx based documentation

In ILCDIRAC-Ops/CreateDoc

Run make completeDocumentation and then rsync -delete -artvu build/html/ /afs/cern.ch/eng/clic/data/doc/ilcdiracDocNew/

or make install to do both things at once.

http://lcd-data.web.cern.ch/lcd-data/doc/ilcdiracDocNew/

Old Epydoc documentation (deprecated)

http://lcd-data.web.cern.ch/lcd-data/doc/ilcdiracdoc/

In the ILCDIRAC basefolder, run

epydoc * ILCDIRAC
cp -r html/* /afs/cern.ch/user/s/sailer/clic/data/doc/ilcdiracDocNew