Skip to content

Commit

Permalink
Drop "Ensure stable Pulp release" instruction
Browse files Browse the repository at this point in the history
Step 2 pointed to Pulp 2, rather than Pulp 3 so it was already out of
date. For the first part it's incomplete if you want to bump the
release. That should happen in nightly anyway and isn't part of
branching.
  • Loading branch information
ekohl committed Aug 23, 2023
1 parent d9cf6a4 commit 13e4b70
Showing 1 changed file with 0 additions and 3 deletions.
3 changes: 0 additions & 3 deletions procedures/katello/branch.md.erb
Original file line number Diff line number Diff line change
Expand Up @@ -46,9 +46,6 @@
- [ ] gpg-key: When it becomes available, get the new Foreman GPG key for the corresponding Foreman version ([example here](https://github.com/theforeman/theforeman-rel-eng/blob/master/releases/foreman/2.5/settings) and put the last 8 characters here
- [ ] tags: update Katello version number in all values. Check the nightly config to see if any tags/repos need to be updated
- [ ] Open a PR to [tool_belt](https://github.com/theforeman/tool_belt) with the new config file
- [ ] Ensure stable Pulp release
- [ ] Update the [katello-repos](https://github.com/theforeman/foreman-packaging/blob/rpm/develop/packages/katello/katello-repos/katello-repos.spec#L1-L2)
- [ ] Update [forklift](https://github.com/theforeman/forklift/blob/master/roles/katello_repositories/defaults/main.yml#L4-L5)
- [ ] Coordinate with installer maintainers that expected changes are completed.
- [ ] [candlepin](https://github.com/theforeman/puppet-candlepin)
- [ ] [pulpcore](https://github.com/theforeman/puppet-pulpcore)
Expand Down

0 comments on commit 13e4b70

Please sign in to comment.