Skip to content

Release Series End-of-Life

When a release reaches end-of-life, we need to discountinue a few items.

  • Remove the retired series from the OSG VMU tests. However, retain the upgrade test from the retired series to the current series.

  • Remove any github actions that build software-base or osg-wn-client Docker images for the retired series.

Previous Release Series Removal Plan

In order to reduce clutter and disk usage on our repositories and build system, we will remove older OSG Software release series. This will result in packages from those series becoming unavailable, so we will remove a release series when its packages are no longer needed.

We will remove a release series no earlier than when the following series is completely out of support. For example, OSG 3.1 will be removed when OSG 3.2 is out of support, and OSG 3.2 will be removed when OSG 3.3 is out of support.


Removing a release series requires work from both Operations and Software & Release. The first step is to create a JIRA ticket in the SOFTWARE project to track the work. Second, Software & Release will enumerate the directories for Operations to remove.

Operations tasks should be completed before Software & Release tasks.


These tasks should be completed in order.

  1. Two weeks in advance, notify sites (including mirror sites) that the release series is going away. See the template email below.

  2. Remove the series from the mash configs on the machines:

    • Add the koji tags for the old series to the /usr/local/osg-tags.excluded file:

      # cd /usr/local
      # fgrep osg-3.1 osg-tags
      # fgrep osg-3.1 osg-tags >> osg-tags.exclude
    • Re-run to update the mash config files:

      # ./
  3. Remove the appropriate repo directories from /usr/local/repo/osg.

    # rm -rf repo*/osg/3.1/
  4. Reclaim space from any cached rpms in the mash cache which are no longer linked elsewhere:

    # find mash/cache/ -name \*.rpm -type f -links 1 -delete
  5. Wait for mash to run and verify that the repos are no longer getting updated:

    • Look at the mash logs in /var/log/repo.
    • Verify that mash did not recreate the repo directory under /usr/local/repo/osg corresponding to the old release series.
  6. Remove tarballs from repo and OASIS

Software & Release

These tasks can be completed in any order.

  • Tag and remove the SVN branch corresponding to the release series.

  • Edit vm-test-runs and remove any "long tail" tests that reference the series.

  • Edit tarball-client:

    • Remove bundles from bundles.ini.
    • Remove patch and other files that were used only by those bundles.
    • Test that the current bundles didn't get broken by your changes.
  • Edit osg-build:

    • Remove the promotion routes from promoter.ini.
    • Remove references in
    • Test your changes; also run the unit tests.
  • Remove things from Koji:

    • All targets referencing the series.
    • All tags referencing the series.
  • Remove references to the series from opensciencegrid/docker-osg-wn on GitHub.

  • Move files in /p/vdt/public/html/release-info to its attic subdirectory.


If we really need RPMs from a removed release series, we can look at the text files in /p/vdt/public/html/release-info/attic to determine the exact NVRs we need, and download them from Koji.

Template Email

Subject: OSG 3.X packages will be removed from the repositories YYYY-MM-DD
On <DAYNAME, MONTH DAY>, the OSG will be removing the OSG <3.X> release
series from our repositories.  This includes both RPMs and tarballs hosted

As a reminder, support for OSG <3.X> ended after <MONTH YEAR>.

If your site is running OSG <3.X>, you should upgrade to the current release
series, OSG 3.Y.  See our upgrade documentation [1] for instructions.  If you
need assistance upgrading, please contact us at [email protected].


If we're dropping support for a distro (e.g. EL 5 when we drop OSG 3.2), add the following after the first paragraph:

Note that OSG <3.X> was the last release that supported Enterprise Linux <Z>
distributions.  If you believe that you still need support for this operating
system series, please contact us at [email protected].

Since we're dropping support for i386 (32-bit) when we drop OSG 3.3, add the following after the first paragraph:

Note that OSG 3.3 was the last release that contained 32-bit packages.  If
you believe that you still need support for this architecture, please
contacts us at [email protected].