Release Management » History » Revision 8
Revision 7 (Sam Kottler, 12/07/2012 12:20 PM) → Revision 8/28 (Greg Sutcliffe, 12/07/2012 12:21 PM)
h1. Release Management For each major (x.0) and minor release there is a release nanny who is responsible for managing communication around releases. This person is responsible for handling the generation of release notes, sending emails and IRC notifications about release candidates and final releases, as well as generally tracking blockers, etc. h2. Release notes h4. Template h2. Communication h4. Email h4. IRC h2. Packaging h4. RHEL derivatives h4. Debian Rasks for each RC release * Update foreman-rpms/deb/<distro>/rc/<package> * As a minimum, update the changelog file, since the package version comes from that * Update build.sh with the SHAsum of the RC tag * Get jenkins to rebuild the packages for the rc repo Stuff to do at release: * Update foreman-rpms/deb/<distro>/stable/<package> * copy from the appropriate RC packaging files * don't copy the rc changelog directly, craft a new one with appropriate release notes * update build.sh with the SHAsum of the release tag * Clean out the rc repo on server09 by hand > * reprepro -b ~/foreman-reprepro -C rc remove squeeze foreman-proxy > * reprepro -b ~/foreman-reprepro -C rc remove squeeze foreman > * reprepro -b ~/foreman-reprepro -C rc remove squeeze foreman-sqlite3 > * ... all the other foreman-* packages ... * - Get jenkins to build rebuild the packages for the stable repo - Building packages after cleanup will deal with rsync to deb.tf.o