First, be sure to read the {link: http://www.cs.wisc.edu/condor/developers/version-history.html Version History Policy and FAQ}. This spells out the policy for the version history and explains a big part of your task at release time: finding missing entries.
-Of course, you can't finalize the version history until the code-freeze for the release and the source is tagged. So, in practice, you'll have to coordinate with the real release wrangler to make sure you'll looking at the right diff.
+Of course, you can't finalize the version history until the code-freeze for the release and the source is tagged. So, in practice, you'll have to coordinate with the real release wrangler to make sure you're looking at the right diff.
Once you've got the official release tag (or the build tag that's going to become the official tag), here's what you do:
