TWiki> EGEE Web>IntegrationProcedure>ProdRelCheck (revision 75)EditAttachPDF

Production Release Check List

Responsible: Pablo Guerrero Backup person: Maria Alandes


The following list must be used in combination with the Integration Procedure twiki that describes all the technical details involved in the release process. This twiki aims to list the necessary steps to create a production release helping to avoid mistakes and decrease human errors.

Check List template

Please, print the following check list templates to go through the production release process:

Pre requirements

Access to machine lxbrf2713 where you have the necessary scripts to create repositories (

Check List

1. Copy the production repo into the prepare area:

cp -pR /afs/ /afs/

2. For each patch in status Ready for Production:

  • Check in the list of associated bugs, if any, that the bug status is Fix certified or Fix not certified. Remove Invalid/Obsolete bugs. Contact certifiers if there are bugs in Ready for test since they should update this status after verifying the bug.

  • Check the release notes again and ask for an improved text to the patch submitter if the quality is poor or the explanations are not very useful.

3. Update the Release field of the patches with 3.X.0 Update *NN*.

4. TODO Insert the patches in the web DB and insert the updated RPMs. Before, be sure the release, architecture, service and service platform have been created.

5. In lxbrf2713, run the script to create the production repository:  -r <release> -o <os> -a <arch> <patch1 [... patchN]>

6. Copy the production repo in the prepare area to the production area:

cd /afs/
rm -Rf R3.X_old
cp -pR  /afs/ R3.X_new 

7. If the release affects the UI and/or the WN, copy the tarballs from the staged rollout area to the production area .

Copy from 

/afs/ or SL5_x86_64) 

/afs/,SL4_x86_64 or SL5_x86_64) 

/afs/,SL4_x86_64 or SL5_x86_64) 
/afs/,SL4_x86_64 or SL5_x86_64) 

8. TODO Create the update, attach the patches, format the release notes and copy the short description to the field for every patch

9. TODO Add any know issues if needed

10. Do a final check of the contents of the release pages:

  • Main page:
    • Check that a summary for each patch is present and well formated.
    • Check the list of patches is complete according to the original mail sent by Operations.
    • Check the priority of patches is correct. If a patch is priority High the corresponding affected services should be in red, stating High.

  • Service specific update pages:
    • Check the release notes make sense for the service and that only the patches affecting the service are actually described.
    • Check the list of rpms is correct by comparing it with the rpm list in the relevant patches.
    • Check the list of bugs is correct by comparing it with the bug list in the relevant patches.
    • Check the URLs of the rpms are correct, in the update page and in the rpm list page (both HTML and txt).

11. FIXME Send a preview mail to project-eu-egee-middleware-emt and gd-release-team. In the subject write Preview 3.X Production Update XX. They'll check that everything is OK and they'll give the green light to publish the release. The mail should be something like:

Dear all,

Please find a preview of the production release notes here:
<< Preview URLs here >>

Any input/feedback provided as a reply to this mail would be valuable and is therefore welcome. 

The Integration Team

12. In case any of the patches provide a fix for a security issue identified by GSVS, contact Lind Cornwall to get the URL for the Security Advice. Modify the web pages to include this URL as soon as it's available.

13. Publish the new repository (every 30min past full hour glitesoft is synchronized):

cd /afs/
mv R3.X R3.X_old
mv R3.X_new R3.X

14. TODO Publish the release notes

15. For each release patch change the Savannah status to In production. Change the attached bugs status to Ready for Review, that's needed also for the bugs attached to the internal patches released. This can be done using the SCLI. Please, download the script in the location where you normally have org.glite.savannah.viewer/cli/:

svn co
cd trunk/

16. If there are new node types released, remember to:

  • Create the repo files under
  • Add in the Generic Install Guide any relevant information about the new node type where needed.

17. Announce the Release using the CIC portal.

  • Go to the CIC portal and select Send a EGEE Broadcast.
  • Then select Broadcast Information from ROC section (although the broadcast form is the same for all).
  • Select News publication in all CIC portal views YES
  • Select glite Annoucement Mailing Lists, OSG, WLCG Tier-1 contacts, VO managers, Production site admins.
  • Add in the CC: gd-release-team.


gLite Release of UPDATE nn to gLite 3. x. Priority: [Normal/HIGH/**URGENT**] 


Dear gLite users,

UPDATE nn for gLite 3.x is now ready for production use.
The priority of the updates is: [Normal/HIGH/**URGENT**]

The highlights of the update are:


All details of the update can be found in:
[COPY AND PASTE updates URL here]

Note that the UI and WN tarballs are available from the UI and WN pages.

Remember to report any issues with this set of updates using GGUS:

Best regards,
The gLite Release Team

18. Announce the release also in the LCG-ROLLOUT.

19. FIXME Check the retirement calendar for 3.1 and update the dates.

20. Put a symlink to empty in the beta repo for the released services.

Topic attachments
I Attachment History Action Size Date Who Comment
Microsoft Word filedoc Prod-check-list.doc r1 manage 72.0 K 2010-08-16 - 16:08 MariaALANDESPRADILLO Check list for Production Releases
Edit | Attach | Watch | Print version | History: r84 | r77 < r76 < r75 < r74 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r75 - 2011-01-17 - unknown
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl 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? Ask a support question or Send feedback