include "archive old debian releases" step in release procedure

procedure

@@ -106,7 +106,8 @@ procedures = {
         debian_full_version: debian_full_version, # 1.20.0~rc1-1
         full_version: full_version, # 1.20.0-rc1
         version: version, # 1.20.0
-        short_version_minus_two: "#{major}.#{minor.to_i - 2}"
+        short_version_minus_two: "#{major}.#{minor.to_i - 2}",
+        short_version_minus_five: "#{major}.#{minor.to_i - 5}"
       )
     end
     opts.on('--foreman-version [X.Y]', /^\d+\.\d+$/, 'Foreman version, for Katello') do |foreman_version|

procedures/foreman/release.md.erb

@@ -164,5 +164,6 @@ Note: If for some reason there was an issue with the tarballs that required uplo
 - [ ] Share the release announcement on Twitter
 <% if is_first_ga -%>
 - [ ] Update `stable` version in [foreman-infra](https://github.com/theforeman/foreman-infra/blob/master/puppet/modules/profiles/manifests/web.pp#L24)
+- [ ] Create an issue in [foreman-infra](https://github.com/theforeman/foreman-infra/issues) to archive old Debian releases (keeping <%= short_version_minus_five %> and newer)
 <% end -%>
 - [ ] Release pipeline will trigger [foreman-plugins-<%= short_version %>-deb-test-pipeline](https://ci.theforeman.org/job/foreman-plugins-<%= short_version %>-deb-test-pipeline/) and [foreman-plugins-<%= short_version %>-rpm-test-pipeline](https://ci.theforeman.org/job/foreman-plugins-<%= short_version %>-rpm-test-pipeline/). These don't block releases but can be used to understand known issues around plugin compatibility with Foreman <%= short_version %>.