TS8 Software Control Plan

overall software version control plan

• Firmware 
  • Will very soon be in github at: https://github.com/lsst-camera-electronics
  • Stefano maintains a confluence page with release notes (where?)
    • Releases should also be tagged in github in future
  • Firmware version number can be read out and-out via DAQ and put into FITS header
• Sequencer
  • A new github repo was created last week for keeping sequencer code
    • https://github.com/lsst-camera-dh/sequencer-files
  • We should make sure all code used by TS-8 is loaded in here (I don't think it was updated after last weeks successful run)
  • We should add some type of checksum or version number to the sequencer so we can track the version in fits headers
• DAQ 
  • Software in in private git repository: https://github.com/lsst-camera-daq
    • Contact jrb@slac.stanford.edu if you need access
  • Release notes are available?
  • Version number can be read out via DAQ and put into FITS header
• CCS
  • All CCS code is in LSST subversion, and releases are tracked via the CCS release process
    • http://srs.slac.stanford.edu/releaseManagement/
  • Version numbers of all CCS systems are available to eTraveler (and are currently recorded?)
    • Note concerning recording of version: It needs to be adapted to include ts8/power subsystems
• Configuration
  • Configuration for test stands are tracked in github:
    • https://github.com/lsst-camera-dh/config_files
    • https://github.com/lsst-camera-dh/release
• eTraveler:
  • Various repositories (portal-web, eTraveler-clientAPI, eTraveler-dbSchema, eTraveler-travelerDefinition, eTraveler-frontend, lcatr-harness, ...) in https://github.com/lsst-camera-dh/
  • Development managed through JIRA.
• eotest
  • https://github.com/lsst-camera-dh/eotest
  • https://github.com/lsst-camera-dh/offline-jobs
  • https://github.com/lsst-camera-dh/harnessed-jobs
  • Development and versioning managed in JIRA
• Visualization
  • FireFly (IPAC) code is here: https://github.com/lsst/firefly
  • Camersa specific code is here: https://github.com/lsst-camera-visualization
  • Need to move to clearer release/installation procedure.
• CCB process
  • The overall software release process for test stand software is the CCB process
    • eTraveler CCB
  • TS8 (and TS5?) are not currently under CCB control, but they should be placed under CCB control before any production running
    • Deployment of above software should all be tracked by CCB before being deployed on production TS5/8