Release Management Project


This project breaks the direct connection between the LCFG include and package files and the individual LCFG profiles of DICE machines, interposing a regime of weekly DICE releases. This allows us to test each DICE release for integrity and stability before it is widely deployed.


All DICE users and all LCFG users.


The new regime offers improved stability for all DICE users, since each DICE release is tested for installation and package update problems before being approved for widespread use.

Computing staff will find that simple problems will be more likely to be spotted and corrected before they affect most machines and users. They also benefit from substantially quicker profile generation whenever a header or package file is changed, since many less machines than before have their profiles generated directly from the core repository files.

The releases also feed into the external distribution of LCFG; external users of LCFG will find it convenient to have a supply of up-to-date, tested, weekly stable releases available for download.


  1. Procedures for making, testing, fixing and deploying testing and stable releases.
  2. Opt-out arrangements for avoidance of release management (the develop and default releases).
  3. LCFG server support for the release management system.
  4. Documentation for computing staff.
  5. Automation of the procedures, as far as is practical.




Chris Cooke (in the Managed Platforms unit) manages the project.





The project is finished and has been signed off by the development meeting.



See Also

Topic revision: r3 - 04 Oct 2006 - 13:26:32 - ChrisCooke
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback
This Wiki uses Cookies