Preproduction Release Check List


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 preproduction 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

The following machines are needed in order to do a production release:

  • glite 3.1, 32bit: SLC4/32bit repo machine with glite-release CVS module, mysql-server and mysql client installed.
  • glite 3.1, 64bit: SLC4/64bit repo machine with glite-release CVS module, mysql-server and mysql client installed.
  • glite 3.2, 64bit: SL5/64bit repo machine with glite-release CVS module, mysql-server and mysql client installed. Remeber to install also your GPG key to sign rpms.

Check List

1. cd glite-release in your repo machine and run cvs update to make sure you have the last version. Make sure that in, GLITE_RELEASE contains the right value of the release you are doing.

2. Check the prepare area is equal to the pps one. Use the check_pps_all script for this. Otherwise delete the current prepare area and copy from pps:

cp -pR  /afs/ /afs/

3. Make sure the previous pps release was properly tagged in CVS. You can do this by checking that the last version of each metapackage in the pps list is tagged in CVS. If not, run the following scripts which wil tag the prod-lists, where NN corresponds to the previous update:

./scripts/list-updated-components -r pps -u NN -p arch
./scripts/make-release -l updateNN.pps -p arch -g

4. If you've done the tag, commit the updateXX.pps file from the previous release into glite-release/update_files/pps/platform.

5. Query Savannah for the patches which are Certified. Note that at this point you should also check all the previous production releases that may have happened before this pps release. If there were fast tracked patches, those patches should also be included in this pps release.

6. For each certified patch:

  • Check that the patch you want to move to PPS doesn't contain any dependency to uncertified patches. If it's the case, the patch shouldn't be included in the PPS release until all its dependencies have been certified.

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

  • At this point the Release notes should be in good shape but double check again and ask for an improved text to the patch submitter if the quality is poor or the explanations are not very useful.

  • Only for SL5:
    • Move the patch into certified (this will involve signing the rpms included in the patch):
      ./scripts/move-patch -s certified -p <platform> PATCHNUMBER
    • Change the status of the patch into Signed.

  • Move the patch into preproduction to update the lists/pps-lists:
       Existing node type: ./scripts/move-patch -s pps -p <platform> PATCHNUMBER
       New node type: ./scripts/move-patch -s pps  -m PPS-METAPACKAGE_NAME -v $GLITE_RELEASE.0-0 PATCHNUMBER
       In this case don't forget to cvs add the new pps-list file.

  • Check the metapackages affected by the patch have included the updated versions of the relevant rpms. Only the affected metapackages listed in the patch should change:
    cvs diff pps-lists/<platform>/*

  • IMPORTANT Make also sure that in case there are metapackage changes, the pps-lists should reflect the correct package list with the added or removed rpm.

  • Commit the changes to the production list:
    cvs commit -m "Applied patch #PATCHNUMBER" pps-lists/<platform>/*

  • Mark the Release field in the corresponding Savannah patch with
    3.1.0 PPS Update <b>NN</b>

7. At this point search in Savannah for all the patches whose PPS Release field is 3.1.0 PPS Update NN. Double check that you don't forget any patch you would like to release!

8. Create the updateNN.pps file:

scripts/list-updated-components -r pps -u NN -p <platform>

The syntax of this file is:

 metapackage-name|old-cvs-tag|old-cvs-version|new-cvs-tag|new-cvs-version| UPDATE 

9. Check the updateNN.pps file:

scripts/print-release updateNN.pps <platform> check

Only the metapackages that may have dependencies on rpms that change in this release should appear. This is difficult to track when the release contains several patches but it's good to do some extra checking at this point. Get familiar with the patches and with the affected metapackages and try to detect some inconsistencies.

10. Make the Release. In 3.1, if there are new node types, then create a symbolic link to the generic folder in the prepare area.

If you don't want to tag the release at this point, please run the command with the option -s.

 scripts/make-release (-s) -l updateNN.pps -p <platform>

You can compare whether the result of running this command is what you expect by using the check_pps_all script. It compares the prepare area with pps and tells you the differences. It's necessary to compare the listed rpms with the rpm lists in the patches that are part of the update. It requires some manual checking.

11. Create the Tarballs. Send a mail to Ricardo and Andreas like this one:

Remember that in PPS we only create the TAR UI.

Subject: UI Tarball for gLite 3.X Update NN to PPS


Hi Ricardo, Andreas,


For gLite 3.1:

PPS-glite-UI-<NEW UI-Version> here:

For gLite 3.2:

groupinstall for
groupinstall version marker for the UI/64:
glite-UI-version-<NEW 64 UI-Version>

Happy tarballing !!


12. Generate the Release Notes.

  • Create a new entry in the PPS Release Notes page.
    3.1.0 PPS Update XX (Under preparation)
  • In he machine where glite-release is available, run (mysql server and client need to be installed for this):
    scripts/ XX
  • Copy and paste the output of this script in the new twiki page. Modify manually:
    • Preface: write a summary of the patches released in this update.
    • Release date: under preparation
    • New Metapackage versions: copy and paste the output of ./scripts/print-release updateXX.pps
  • Verify in the new page that:
    • All the patches that are released are listed. Compare with Savannah query output.
    • All the metapackages to be reconfigured are correct. This needs to be done by checking each Savannah patch.
    • All the metapackages to be restarted are correct. This needs to be done by checking each Savannah patch.

13. When the tarballs are ready, copy the pre-production release from the prepare area:

cd /afs/
rm -Rf 3.1_old
cp -pR /afs/ \
ln -s  3.1_UXXPPS 3.1

14. Modify the release date in the general PPS Release Notes page and in the page relevant for this update. Also consider to remove links to previous updates in the general page.

15. For each release patch change the Savannah status to "In PPS deployment test".

16. Announce the release to PPS. The mail should be something like:

The announcement is usually a mail reply to a GGUS ticket created by PPS Team with the list of patches which should go to PPS. The mail should be addressed to: pps-support (PPS Coordination); pps-deployment-test;; pps-apt-repository-update.

A template for answering this mail :

Dear all,

The gLite 3.X.0 PPS Update NN is ready. Please find related information here:


17. Remove from /afs/ all patches released in this update.

-- MariaALANDESPRADILLO - 22 Jan 2009

Edit | Attach | Watch | Print version | History: r25 < r24 < r23 < r22 < r21 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r25 - 2009-10-06 - MariaALANDESPRADILLO
    • 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