This page describes the release process for new versions of debian-installer and ubiquity.

== debian-installer ==
'''TODO'''

== ubiquity ==
 1. Run {{{debconf-updatepo}}} and commit the result, if any, of that.
 1. Run {{{./debian/rules update}}}, then check and commit the result.  It's important to not commit runs of {{{./debian/rules update}}} until you're ready to release, as failing to creates noise in the history.
 1. Run {{{dch -r}}} then {{{debuild -S}}}.  Grab the source of the version of ubiquity in the archive by running {{{apt-get source ubiquity}}}, then run {{{debdiff}}} against the archive version and your just built copy, and pipe it into your editor of choice to review the changes.  It's often helpful to use filterdiff to remove translation noise.  For example:<<BR>>
 {{{debdiff /tmp/ubiquity_1.13.8.dsc ~/bzr/ubiquity_1.13.9.dsc | filterdiff -x 'debian/po/*.po' -p1 | view -}}}
 1. If your review of the {{{debdiff}}} does not uncover any problem code or files that do not belong in the package (temporary files created by your editor, for example), sign and upload the package to the archive by running {{{debsign}}} and {{{dput}}} on the {{{.changes}}} file, in that order.
 1. If in your review of the debdiff you notice major new features or new preseed questions, it's worth noting them in a message to <<MailTo(ubuntu-installer AT lists DOT ubuntu DOT com)>>.
 1. If the next ubiquity release is going to be in a new release of Ubuntu, bump the minor version in configure.ac, then run ./autogen.sh and commit.