Project

General

Profile

Actions
History

Development Resources »

Release Process » History » Revision 124

« Previous | Revision 124/211 (diff) | Next »
Dominic Cleal, 03/03/2015 07:23 AM
three plugin versions simultaneously

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.

First steps

  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 Releases, 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
    • create public custom query with target version set, sorted by status ascending, then priority descending
  8. Go through targeted features in redmine and align features with our backlog

Before creating branch in git

  1. Announce beginning of bug-squashing to foreman-dev (example)
  2. Copy website manual content (theforeman.org repo) from previous version to this version (example)
  3. Update manual if applicable for any additional installation steps
  4. Draft release notes in markdown (example) using roadmap, with these sections (and do not use personal pronouns):
    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 (helper vim search and replace command bellow)
    4. CLI release notes are taken from the hammer-cli and hammer-cli-foreman changelogs
    5. Link to installer changelogs and note the rough versions being used
  5. Check git log for any changes without associated bug number and add to release notes if applicable (https://gist.github.com/lzap/6520535)
  6. Refresh kickstart, snippet and partition table templates from the community-templates repo to Foreman core
  7. Clone tags and create build targets in Koji using koji/copy-tags-commands.sh in foreman-packaging/rpm/develop
    • foreman-1.2-rhel6 etc. as clones of nightly tags
    • foreman-plugins-1.2-rhel6 etc. with inheritance from the new Foreman tags
    • Untag all git/nightly builds: for t in foreman-1.2-rhel6 foreman-1.2-nonscl-rhel6 foreman-1.2-rhel7 foreman-1.2-nonscl-rhel7 foreman-1.2-fedora19; do kkoji list-tagged $t | grep git | awk '{print $1}' | xargs kkoji untag-build $t; done
    • check for non-SCL packages that might be in the SCL tags and untag them, else these will cause mash precedence issues
      • for t in foreman-1.2-rhel6 foreman-1.2-rhel7; do kkoji list-tagged $t --quiet | egrep "^(rubygem-|foreman)" | awk '{print $1}' | xargs kkoji untag-build $t; done
  8. Create mash scripts and configuration on Koji
    • copy /usr/local/bin/foreman-mash-split-1.*.py to foreman-mash-split-1.2.py, update the OSes and version numbers at the bottom
    • copy /etc/mash/foreman-1.*-*.mash, update the version numbers, add/remove files for OS changes
  9. Add new plugin tags (i.e. 1.2) to Koji plugins mash script (foreman-mash-split-plugins.py), remove old ones (keep three)
  10. Add version (1.2) to release_plugins_push job (note, it will be added to tests later), remove old ones (keep three)
  11. Clone Debian nightly repos to 1.2 using copy/freight instructions
  12. Add release to "Found in release" list in redmine: http://projects.theforeman.org/custom_fields/4/edit

Helper vim command to replace all (#1234) bugs with links:

%s/(\(#\)\([0-9]\+\))/(\[\1\2]\(http:\/\/projects.theforeman.org\/issues\/\2))/g

Pre-release candidates

When ready to branch for release candidates.

  1. Make releases of installer modules, usually new minor or major versions
  2. Add new languages that are at a reasonable completion on Transifex to develop
  3. In foreman develop run make -C locale tx-update
  4. In foreman, smart-proxy, foreman-installer and foreman-selinux branch develop to 1.2-stable (from this point cherry-picks into this branch only from this point using: git cherry-pick -x SHA)
  5. In foreman-installer, branch 1.2-stable,
    1. change Puppetfile from git references to specific version ranges (e.g. >= 1.3.1 < 1.4.0)
  6. In foreman-packaging for RPMs:
    1. branch rpm/develop to rpm/1.2
    2. on rpm/1.2, in rel-eng/releasers.conf and rel-eng/tito.props, replace "nightly" with "1.2"
    3. on rpm/develop, change foreman/foreman-proxy/foreman-installer/foreman-selinux version to 1.3.0, add %changelog entry
  7. In foreman-packaging for debs:
    1. on deb/develop, update debian/*/*/changelog with entries from 1.1, commit with message "Sync 1.1.x releases into changelogs"
    2. branch deb/develop to deb/1.2
    3. on deb/develop, run scripts/changelog.rb -v 1.3.0-1 -m "Bump changelog to 1.3.0 to match VERSION" debian/*/*/changelog
  8. In foreman develop commit with message "Bump version to 1.3-develop":
    1. change to VERSION to 1.3.0-develop
    2. run extras/changelog
  9. In smart-proxy develop commit with message "Bump version to 1.3-develop":
    1. change to VERSION to 1.3.0-develop
    2. run extra/changelog
  10. In foreman-selinux develop commit with message "Bump version to 1.3-develop":
    1. change to VERSION to 1.3.0-develop
    2. run extras/changelog
  11. In foreman-installer develop commit with message "Bump version to 1.3-develop":
    1. change to VERSION to 1.3.0-develop
  12. Update foreman-dev with translations status to encourage 100% translations before release, announce string freeze date
  13. Change Transifex resource URL to point to the 1.2-stable branch
  14. Set up test_1_2_stable job on Jenkins, copy from existing stable or test_develop (don't use dots in the name, it breaks)
  15. Set up test_proxy_1_2_stable job on Jenkins in the same way
  16. Update release notes in new website manual version
  17. Generate a release GPG key using GPG_Keys
    • publish to keyserver
    • security.md on the website
    • create releases/1.2/RPM-GPG-KEY-foreman on yum.theforeman.org
    • update koji's /etc/mash/foreman-1.2-*.mash with GPG key ID

For each release candidate

  1. Make patch releases of installer modules that have important changes
  2. Compare tagged packages in nightly vs. release koji tag and re-tag any updated dependencies that are required
  3. In foreman 1.2-stable run make -C locale tx-update
  4. In foreman 1.2-stable commit with message "Release 1.2.0-RC1":
    1. change VERSION to 1.2.0-RC1
    2. run extras/changelog
  5. In smart-proxy 1.2-stable commit with message "Release 1.2.0-RC1":
    1. change VERSION to 1.2.0-RC1
    2. run extra/changelog
  6. In foreman-selinux 1.2-stable commit with message "Release 1.2.0-RC1":
    1. change VERSION to 1.2.0-RC1
    2. run extras/changelog
  7. In foreman-installer 1.2-stable commit with message "Release 1.2.0-RC1":
    1. change VERSION to 1.2.0-RC1
  8. Tag commits in foreman, smart-proxy, foreman-installer and foreman-selinux: git tag -m "Release 1.2.0-RC1" 1.2.0-RC1
  9. Push to the project repos: git push project && git push project 1.2.0-RC1
  10. Run the Jenkins Release Pipeline to create tarballs
  11. Verify tarballs are present on downloads.theforeman.org, download, sign and upload detached signatures
    1. gpg --homedir gnupg/1.2 -b -u packages@theforeman.org foreman-1.2.0-RC1.tar.bz2 (requires 1.2 release GPG key generated above)
  12. In foreman-packaging rpm/1.2 branch, change foreman.spec, foreman-proxy.spec, foreman-selinux.spec, foreman-installer.spec:
    1. set version to "1.2.0", release to "0.1%{?dotalpha....", uncomment alphatag* (replace # with %), change to RC1
    2. change foreman/foreman.repo URLs from /nightly to /releases/1.2, change "nightly" in name to "1.2" and enable gpg checking
    3. change foreman/foreman-plugins.repo URLs from /plugins/nightly to /plugins/1.2, change "nightly" in name to "1.2" and DO NOT enable GPG checking
    4. update foreman/foreman.gpg with the release public key
    5. in each package dir, run spectool -g *.spec and git annex add *.tar.bz2
    6. commit with message "Release 1.2.0-RC1"
    7. perform RPM scratch build of each project (see RPM_Packaging)
    8. tag each project with tito tag --keep-version --auto-changelog-message "Release 1.2.0-RC1"
  13. Debian_Packaging: Update changelog files with appropriate data
  14. Trigger next step of release pipeline: release_packages
  15. Update theforeman.org sections:
    1. _includes/social.html version number
    2. _includes/header.html manual links
  16. Follow "Publishing releases" below

For final release

  1. Make patch releases of installer modules that have important changes
    • Branch to MAJ.MIN-stable if recent changes to the module aren't suitable for patch (x.y.z) release
  2. Compare tagged packages in nightly vs. release koji tag and re-tag any updated dependencies that are required
  3. In foreman 1.2-stable run make -C locale tx-update
  4. In foreman 1.2-stable commit with message "Release 1.2.0":
    1. change VERSION to 1.2.0
    2. run extras/changelog
  5. In smart-proxy 1.2-stable commit with message "Release 1.2.0":
    1. change VERSION to 1.2.0
    2. run extra/changelog
  6. In foreman-selinux 1.2-stable commit with message "Release 1.2.0":
    1. change VERSION to 1.2.0
    2. run extras/changelog
  7. In foreman-installer 1.2-stable commit with message "Release 1.2.0":
    1. change VERSION to 1.2.0
  8. Tag commits in foreman, smart-proxy, foreman-installer and foreman-selinux: git tag -m "Release 1.2.0" 1.2.0
  9. Push to the project repos: git push project && git push project 1.2.0
  10. Run the Jenkins Release Pipeline to create tarballs
  11. Verify tarballs are present on downloads.theforeman.org, download, sign and upload detached signatures
    1. gpg --homedir gnupg/1.2 -b -u packages@theforeman.org foreman-1.2.0.tar.bz2 (requires 1.2 release GPG key generated above)
  12. In foreman-packaging rpm/1.2 branch, change foreman.spec, foreman-proxy.spec, foreman-selinux.spec, foreman-installer.spec:
    1. set version to "1.2.0", release to "1%{?dotalpha....", comment alphatag* (replace % with #)
    2. in each package dir, run spectool -g *.spec and git annex add *.tar.bz2
    3. commit with message "Release 1.2.0"
    4. perform RPM scratch build of each project (see RPM_Packaging)
    5. tag each project with tito tag --keep-version --auto-changelog-message "Release 1.2.0"
  13. Debian_Packaging: Update changelog files with appropriate data
  14. Trigger next step of release pipeline: release_packages
  15. Update theforeman.org sections:
    1. _includes/social.html version number
    2. _includes/header.html manual links
    3. _layouts/homepage.html quickstart link
    4. _layouts/manual.html latestversion
    5. _config.yml quickstart link
  16. Merge develop branches into master (git merge -Xtheirs --no-ff) for: foreman, smart-proxy, foreman-installer, foreman-selinux
    • Skip for now, this doesn't seem to work reliably
  17. Follow "Publishing releases" below

Publishing releases (RCs and final)

  1. Final only: update $latest class parameter on web class to point to the new version number (see foreman-infra/puppet/modules/web/manifests/init.pp)
  2. First RC: add version (1.2) to release_plugins_test jobs/job/release_plugins_test job
  3. Send announcement e-mail to foreman-announce, CC foreman-users, set reply-to to foreman-users
  4. Link to announcement e-mail on IRC, Google+ and update IRC /topic
  5. Update Wikipedia Foreman entry at: https://en.wikipedia.org/wiki/Foreman_(software)
  6. Add release to "Found in release" list in redmine: http://projects.theforeman.org/custom_fields/4/edit

After final release

  1. Sync translations from Transifex into develop and update i18n
  2. Remove target version from all issues assigned to the current release, unless they will be fixed in a future point release

Updated by Dominic Cleal about 9 years ago · 124 revisions