h1. 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.

h2. Pre-release

# Select the release nanny

# Ensure RPM and Debian nightly packages are in good shape and all RPM dependencies are up to date

# Decide on the version number

# If number has changed, update version number in redmine

# Add _next+1_ anticipated version number to redmine under "Settings":http://projects.theforeman.org/projects/foreman/settings, sharing "With subprojects"

# Check "roadmap":http://projects.theforeman.org/projects/foreman/roadmap and issue search ("example":http://projects.theforeman.org/projects/foreman/issues?fixed_version_id=24&set_filter=1&status_id=o)

#* 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

# Announce beginning of bug-squashing to foreman-dev ("example":http://groups.google.com/group/foreman-dev/browse_thread/thread/769d9060774da864)

h2. Pre-release candidates

# Request creation of tags and build targets in "Koji":http://koji.katello.org/koji from rel-eng (foreman-1.2-rhel6 etc.)

# Branch develop to 1.2-stable

# 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)

# Re-tag all dependencies in Koji to the release tag (@kkoji tag-pkg foreman-1.2-rhel6 <pkg>...@)

h2. For each release candidate

# 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

# Perform scratch build and then tag and release real build of foreman and foreman-proxy