If the =V7_0_2= tag doesn't exist yet, use the appropriate build tag, e.g. =BUILD-V7_0_2-branch-2008-6-9=.
1: Go through the saved output (e.g. =7.0.2-diff=) and make sure everything in there that should be documented has a corresponding entry in the version history.
1: If you find parts of the diff that should be documented which are missing, make a list of the missing entries and who committed the changes.
+1: A development release will normally have several fixes from the concurrent stable branch, so it should have a version history item that indicates this. Something like "This release contains all bug fixes from Condor version 7.6.2." in the 7.7.0 version history.
1: Once you've gone through the entire diff, email your list of missing entries to condor-team@cs.wisc.edu for public humiliation and so that people know how much they owe to the version history pizza fund (see the {link: http://www.cs.wisc.edu/condor/developers/version-history.html policy/FAQ}). You can either add the missing entries yourself, or get the guilty parties to do it.
That's the whole task. However, give yourself at least a day to do it, since the diff can be huge and this is a time consuming process. Once you're done, notify the "real" release wrangler so they know when it's safe to publicly release the manual.
