Make this post a wiki (help)
Roles
One Month Prior to Branch Date
Release Owner
- Start attending upstream release sync meetings and giving updates
- Announce upcoming branching to Discourse development category 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
- Install grunt
-
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 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
Release Owner
- Ensure that issues requiring installer changes are merged
Two Weeks Prior to Branch Date
Release Owner
-
Add tool_belt config for new release:
- Create a new yaml file using the nightly Katello config as a template: tool_belt configs
-
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)
- mash_scripts: update Katello version number in all values
- 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)
- gpg-key: When it becomes available, get the new Foreman GPG key for the corresponding Foreman version (example here 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 with the new config file
-
Ensure stable Pulp release
- Update the katello-repos
- Update forklift
- Coordinate with installer maintainers that expected changes are completed.
- Review the Foreman schedule and planning (example) and note the date of the first scheduled release candidate.
Release Engineer
-
Ensure tool_belt config is merged and output from
./tools.rb koji configs/katello/4.10.yaml
matches expectations
On Branch Date
Release Owner
- Create KATELLO-4.10 branch using branch_project
- Push KATELLO-4.10 branches using branch_push
- Bump versions to 4.11-master using develop_branch_bump
- Push version bumps to 4.11-master using develop_branch_push
- Bump Katello related packages to their next versions
-
Generate and post the release procedure, if not already posted:
- (Note that Katello uses dots instead of dashes for release candidates, e.g. 4.1.1.rc1 not 4.1.1-rc1)
-
Make sure to run
./tools.rb setup-environment
first -
Run
./tools.rb procedure release katello 4.10.0.rc1 <%= target_date %> @David @pcreech
in tool_belt -
Post the output in Development/Releases using
Katello 4.10.0-rc1 release process
- Clone GitHub - theforeman/apidocs: API documentation for Foreman and its plugins 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 4.11.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 4.10.0 TODO” custom query using the last one as a template
Release Engineer
-
Run
./tools.rb koji configs/katello/4.10.yaml --confirm
from tool_belt to create Koji tags -
Run
./tools.rb mash-scripts configs/katello/4.10.yaml
from tool_belt to create Koji mash configs and open PR to tool_belt to commit -
Copy mash configs to Koji
scp mash_scripts/katello/4.10/*.mash root@koji.katello.org:/etc/mash/