Release Process¶

For each major release (i.e. not patch releases), the project selects a "release nanny" who's responsible for taking the develop branch through to release.

Please amend these lists as you see free, and as you find what works and what doesn't work.

Pre-release¶

1. Select the release nanny
2. Ensure RPM and Debian nightly packages are in good shape and all RPM dependencies are up to date
3. Ensure Transifex project is up to date
4. Decide on the version number
5. If number has changed, update version number in redmine
6. Add next+1 anticipated version number to redmine under Settings, sharing "With subprojects"
7. Check roadmap and issue search (example)
   • reassign major features to next+1 version or remove version
   • assign relevant bugs to this upcoming release
   • multiple bugs can be managed using checkboxes and then right clicking on the boxes for a menu
8. Announce beginning of bug-squashing to foreman-dev (example)
9. Copy website manual content (theforeman.org repo) from previous version to this version (example)
10. Update manual if applicable for any additional installation steps
11. Draft release notes in markdown (example) using roadmap, with these sections:
    1. Headline features: half a dozen important features with a few sentences description each
    2. Upgrade notes: all important notices that users must be aware of before upgrading
    3. Release notes: bullet point list by category of most changes, excluding bug fixes for issues introduced during the release cycle, include link to bug numbers
12. Check git log for any changes without associated bug number and add to release notes if applicable
13. Request creation of tags and build targets in Koji from rel-eng (foreman-1.2-rhel6 etc.)

Pre-release candidates¶

When ready to branch for release candidates.

1. In foreman, smart-proxy and foreman-install, branch develop to 1.2-stable
   • cherry-picks into this branch only from this point using: git cherry-pick -x SHA
2. Commit change to VERSION in develop to 1.3 (next+1 version) and foreman.spec + foreman-proxy.spec to 1.3.9999 (next+1 version)
3. Re-tag all dependencies in Koji to the release tag (kkoji tag-pkg foreman-1.2-rhel6 PKG...)
4. Update foreman-dev with translations status to encourage 100%25 translations before release, announce string freeze date
5. Update $repo in both foreman-installer/foreman and foreman_proxy modules to "rc" (example)

For each release candidate¶

1. Commit change to VERSION in 1.2-stable to 1.2.0-RC1 and foreman.spec + foreman-proxy.spec version to 1.2.0 and release to RC1
2. Update version and dependency versions in all foreman-installer submodules
3. Update submodules on foreman-installer's develop branch
4. Tag commits in foreman, smart-proxy and foreman-installer as 1.2.0-RC1
5. Perform scratch build and then tag and release real build of foreman and foreman-proxy (see RPM_Packaging)
6. FIXME: update Debian build script with tag and trigger Debian build
7. Build foreman-installer modules from develop (see Installer_Packaging workflow)
8. Build foreman-installer RPM and Debian packages from develop (see RPM_Packaging and Debian_Packaging)

For final release

1. Update version and dependency versions in all foreman-installer submodules
2. Revert $repo in both foreman-installer/foreman and foreman_proxy modules to "stable" (example)
3. Update submodules on foreman-installer's develop branch
4. Merge foreman-installer's develop branch into master
5. Build foreman-installer modules from master (see Installer_Packaging workflow)
6. Build foreman-installer RPM and Debian packages from master (see RPM_Packaging and Debian_Packaging)