Before a release is built, please do this list of things:
- Look at the documentation in the docs directory and update it as necessary.
- Ensure the release is properly tested first!
- Ensure that all the correct images are in the Images directory (/atlas/daq/code/Images is where they need to go .. but JOHNAND BRUCE know where they come from maybe /usera/sctrod/AlanWorking?/sctroddaq/installed/confing/Images/RevE?.... maybe) and appropriate test data is in the SctTestApiData directory. Here is an ExampleRodFirmwareReadme file I.
- Decide on branching/tagging naming policy .. which files count which dont, whos dir are you going to use ... will you use the HEAD or some branch?
- Tag all of the files that are used. The tag should be of the form SctRodDaq_X_XX_Something. E.g. SctRodDaq_3_0 or SctRodDaq_3_01_Beta. Outside of the SctRodDaq files this only means the following four dirs VmeInterface, RodDaq/CommonWithDsp, RodDaq/RodCrate, RodDaq/RodUtils directories.
- At Cambridge, log in as "atlasdaq"
- Goto the directory "/atlas/daq/"
- Source the bash setup script "setup_gcc32.sh" (or "setup_gcc32_forOldOnline19_or_Release_3Branch.sh" if you are building a release against online19 e.g. a release in the 3_0_BRANCH or below)
- Change to the code directory
- Change to the gcc32 directory
- Modify the Makefile so it checks out from the tag you have made
- Get an AFS token (klog)
- Decide whether you would like the makefile to run the SystemTests or not.
- Type: "make >& make.out&" and hope that everything works
- The source and binary releases are in the SctRodDaq directory called SourceRelease.tar.gz and BinaryRelease.tar.gz.
- Rename them, do some tests (see TestingARelease) and send them to the appropriate place