Release Testing


The Release Testing is a complementary step of the process of releasing middleware Updates to the production system.

Before the middleware updates are released to the public, they are delivered to a number of selected production sites. The sites apply the update to one or more of their grid services and provide feedback to the release managers.


glite Release Team --> SA1 release testing team: notification

The Release Testing Team (members of receive from the glite Release Team a notification (*) of the upcoming middleware update before the release broadcast is out.

The yum repository to be used to download the rpms is

this location will be available only for the appropriate time window and will be renamed when the update is officially released

Alternative repositories to be used can be specified in the notification(*)

SA1 release testing team --> gLite Release team: feedback

Feedback on the installation has to be provided to the gLite Release Team via the appropriate channel(*). There are no constraints set by the release process on the time for the production of test results. However is reasonable to expect that a test, once started, should not exceed the duration of one working day. the gLite release manager can decide whether to wait for the results or not at his/her discretion. The decision of course depends on the content of the release and on other variables.

As soon as a member of the Release Testing team starts the test a notification (*) is sent to the gLite Release Team to acknowledge that the test on a a package has started

Another reply(*) with the test results is sent after the test is performed.

(*) All the communication between the two teams happens through the 'Prod-Update E-mail' ).
  • Header: The header of this e-mail is defined in the gLite release procedure.
  • Subject: The message is crafted in a way that all replies are logged in a GGUS ticket used to track the release.
  • To: As this e-mail serves many interfaces, it is important that ALL the original recipients are left unchanged in the reply (reply-all)
  • Body: For a better visualisation of the history in GGUS when replying to the 'Prod-Update E-mail' the content of the previous messages should be removed
  • The GGUS ticket is closed by SA1 after the broadcast to production is sent, but updates can still be made after closure.

Sites currently working in Release Testing

Partners sites involved in Release testing are listed in the table below:

Failed to include URL Not Found

Sites willing to join the Release Testing Team can contact

This topic: LCG > WebHome > LCGGridDeployment > GLitePreProductionServices > EGEE_PPS_Coordination > PPS_Current_Programs > PPS_Release_Testing
Topic revision: r4 - 2008-12-17 - AntonioRetico
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2022 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