Release Cycle

To better organize the production of release ALPHA, a release procedure was defined by CERN and CNR and agreed by all WP1.8 members. The objective of this procedure is to organize the different steps of the production of a new DLIGENT release, who is responsible for each step and what tools should be used.

The defined steps are:

  • Available: the developers make the software available for integration
  • Built: the integration team builds the software
  • Integrated: the integration team checks if the software can be deployed
  • Testing: the testing team runs system and functional tests on the software
  • Certified: the TSM verifies if the software is compliant with the CL model
  • Released: the integration team makes the software available

The following picture shows the above topics and highlights the transitions between each step:

Slide0023.gif

At any stage of the Release Process a component can be associated the CANCELLED status in case it cannot be included in the current release for any reason. The reason will be included in a note associated to the component. This does not imply that the same component will not be considered for inclusion in the following release.

Deployment testing:

  • libraries are not submitted to this activity. Integrated state is assigned automatically.
  • services that need manual configuraion are integrated and a note is assoaciated to them.



-- PedroAndrade - 22 Nov 2006

Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2006-12-08 - RobertaFaggian
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    DILIGENT All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback