Releases and Snapshots of the Timing System
A Timing Firmware Release packs together new features and requirements defined in our Development Road Map
as well as bug-fixes from previous releases. Since a Timing Firmware Release should've been tested and integrated with the rest of the Control System:
- Bug-fixes are going to be added to the Release Candidate during the integration and testing phase.
- Release Support in Production. Problems in Production should be reproducible in our test system and be fixed.
These bug-fixes will be presented in the next Snapshot or Release.
Our release cycle is synchronized with the CSCO Development Road Map
and follows the next steps:
- Development Version (Alpha) tested continuously in the Timing Test Facility
- Release Candidate tested in the Timing Test Facility
- Deployment of Release in Production
The Releases have a name where the first letter indicates the version order according to the alphabet:
nigma , F
A Timing Firmware Snapshot packs together the features needed for a particular user-case or particular system (e.g. CRYRING) and it doesn't go through a
completely firmware release cycle. You can see a firmware Snapshot as a Beta Version which is going to be tested in "production system" while
the development goes on, it means:
- Best effort support. We can't guarantee that we will be able to reproduce reported bugs.
- Bug-fixes are NOT going to be added to the Snapshot and rolled out. These bug-fixes will be included in the next Snapshot or Release.
The Snapshots complete a short development cycle:
- Snapshot Candidate tested in the Timing Test Facility
- Deployment in Production
The snapshots don't receive a name and are just completed with the month and year of their creation.
Releases and Snapshots
This includes hardware, gateware, firmware and software. Here is some information on the version history
Timing Receivers including SCU
Hardware and Release Compatibility Matrix
- 19 Nov 2019