View on GitHub

Open Source Cluster Application Resources

Download this project as a .zip file Download this project as a tar.gz file

Documentations > Developer Documentations > Release Management

Release Processes

  1. Make sure to unit tests can run successfully (running run_unit_test).

  2. Prepare documentations

    1. Write and update Installation/Administration guide documentations accordingly.
    2. Generate the Installation Manual PDF. For that, log into the OSCAR Trac system (https://svn.oscar.openclustergroup.org), and go under Admin->WikiToPdf, select the following pages and export to PDF: InstallGuideIntroduction, InstallGuideReleaseNotes, InstallGuidePreparing, InstallGuideNetwork, InstallGuideClusterInstall, InstallGuide/Appendices, InstallGuide/Appendices/NetworkBooting, InstallGuide/Appendices/SISBoot, InstallGuide/Appendices/Tips.
    3. Generate the Management Manual PDF. For that, log into the OSCAR Trac system (https://svn.oscar.openclustergroup.org), and go under Admin->WikiToPdf, select the following pages and export to PDF: AdminGuide, AdminGuide/Introduction, AdminGuide/Wizard, AdminGuide/Commands, AdminGuide/Packages, AdminGuide/Licenses, AdminGuide/Licenses/C3, AdminGuide/Licenses/DisableService, AdminGuide/Licenses/LAM, AdminGuide/Licenses/Maui, AdminGuide/Licenses/MPICH, AdminGuide/Licenses/pFilter, AdminGuide/Licenses/PVM, AdminGuide/Licenses/SIS, AdminGuide/Licenses/Switcher, AdminGuide/Licenses/Torque.
    4. Write and update release notes.
    5. Put the pdf files and the release notes to the OSCAR SVN repository.
    6. In SVN, update the VERSION file.

  3. Make sure the following updates are done:

  4. Update the oscar-base.spec.in file (you may want to update the release number) and the Debian changelog (executing the _dch -v _ command).
  5. Update the OSCAR ChangeLog file.

  6. Update the list of supported distros.

  7. Tag the working branch.

  8. Tag the current working branch to http://svn.oscar.openclustergroup.org/svn/oscar/tags
  9. The naming rule of the tag is “rel”-[VERSION_NUMBER]-[BETA_NUMBER]
    • [VERSION_NUMBER] is the version number of OSCAR that we are going to release and dash(-) would be used to connect the major version number and the minor version number[[BR]] (e.g., for OSCAR 5.1, it would be 5-1)
    • [BETA_NUMBER] is numbered beginning with “b” and followed by the number. The starting number is 1 and it increases one by one if we increases the beta number

  10. If everything seems to work fine on the beta tarball, another tag should be made without [BETA_NUMBER] in order to tag for the release version

  11. Generate new binary packages for supported Linux distributions and upload them on the official OSCAR repositories.

  12. Post announcements. Email to the announce/devel lists to announce the release