branch.md.erb

## Roles

* Release Owner: <%= owner %>

# Four Weeks Prior to Branch Date: <%= four_weeks_before %> to <%= four_weeks_before + 4 %>

## Release Owner

- [ ] Start attending upstream release sync meetings and giving updates
- [ ] Announce upcoming branching to [Discourse development category](https://community.theforeman.org/c/development/9) a month before
- [ ] Update Katello Transifex translations:
  - [ ] Create a Transifex account and join the Foreman team
  - [ ] Spin up a Foreman and Katello installation
  - [ ] [Configure the Transifex client](https://projects.theforeman.org/projects/foreman/wiki/Translating#How-to-pull-translations)
  - [ ] [Install grunt](https://github.com/Katello/katello/blob/master/engines/bastion_katello/README.md)
  - [ ] `grunt i18n:extract` in the katello/engines/bastion_katello directory
  - [ ] `tx pull --minimum-perc 50 --all` in the katello directory
  - [ ] `make -C locale tx-pull` in the katello directory
  - [ ] `grunt i18n:compile` in the katello/engines/bastion_katello directory
  - [ ] `bundle exec rake plugin:gettext[katello]` in the foreman directory
  - [ ] `bundle exec rake plugin:po_to_json[katello]` in the foreman directory
  - [ ] `make -C locale commit-translation-files` in the katello directory
  - [ ] Add any uncommitted translation files and open a PR to Katello (no Redmine issue needed)

# Three Weeks Prior to Branch Date: <%= three_weeks_before %> to <%= three_weeks_before + 4 %>

## Release Owner

- [ ] Ensure that issues requiring installer changes are merged

# Two Weeks Prior to Branch Date: <%= two_weeks_before %> to <%= two_weeks_before + 4 %>

## Release Owner

- [ ] Commit the [settings file](https://github.com/theforeman/theforeman-rel-eng/blob/master/releases/katello/<%= release %>/settings) to the `theforeman-rel-eng` repository. See an example [here](https://github.com/theforeman/theforeman-rel-eng/commit/29b6b92e82de25c7a0e32fb9ca36468d8df0f6a1)
- [ ] Add tool_belt config for new release:
  - [ ] Create a new yaml file using the nightly Katello config as a template: [tool_belt configs](https://github.com/theforeman/tool_belt/tree/master/configs/katello)
  - [ ] Manually update the following sections:
    - [ ] releases: update to current release.  Move the previous 'current' release to prior_releases below.
    - [ ] prior_releases: Remove the oldest prior_release (check with that release owner first to see if there's a reason it should stay)
    - [ ] repos: Update branch names to current versions, including any new releases that need to happen
    - [ ] ignores: Delete all items from this list and start fresh (this will be used for cherry-picks later)
    - [ ] 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
- [ ] Coordinate with installer maintainers that expected changes are completed.
  - [ ] [candlepin](https://github.com/theforeman/puppet-candlepin)
  - [ ] [pulpcore](https://github.com/theforeman/puppet-pulpcore)
  - [ ] [foreman_proxy_content](https://github.com/theforeman/puppet-foreman_proxy_content)
  - [ ] [katello](https://github.com/theforeman/puppet-katello)
- [ ] Review the Foreman schedule and planning ([example](https://community.theforeman.org/t/foreman-2-5-schedule-and-planning/22219)) and note the date of the first scheduled release candidate.

# Branching: <%= target_date %>

## Release Owner

- [ ] Create the KATELLO-<%= release %> branch using <%= rel_eng_script('branch_project') %>
- [ ] Push the KATELLO-<%= release %> branch using <%= rel_eng_script('branch_push') %>
- [ ] Bump versions to <%= develop %>-master using <%= rel_eng_script('develop_branch_bump') %>
- [ ] Push version bumps to <%= develop %>-master using <%= rel_eng_script('develop_branch_push') %>
- [] Bump Katello related packages to their next versions
  - [] [packaging](https://github.com/theforeman/foreman-packaging/pull/8729/files)
- [ ] Set GitHub Actions to use the new branch: `sed -i '/foreman_version/ s/develop/<%= foreman_version %>-stable/' .github/workflows/*.yml`
- [ ] Generate and post the release procedure, if not already posted:
  - [ ] Use <%= rel_eng_script('procedure_release') %>: `PROJECT=katello VERSION=<%= release %> ./procedure_release "<%= target_date %>" "<%= owner %>" "<%= engineer %>"`
  - [ ] Post the output in [Development/Releases](https://community.theforeman.org/c/development/releases/20) using `Katello <%= release %>.0-rc1 release process`
  - [ ] Clone https://github.com/theforeman/apidocs and follow the Katello README section to update the API documentation.
- [ ] Prepare "Katello Next" and future redmine versions
  - [ ] Rename the "Katello Next" release to Katello <%= develop %>.0
  - [ ] Recreate the "Katello Next" release and indicate that it is a placeholder for issues belonging to the next version of Katello
  - [ ] Create the "Katello <%= release %>.1 TODO" custom query using the last one as a template