git log -p V7_0_1..V7_0_2 > 7.0.2-diff
{endcode}
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: 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. The following is some git scripting to help in this.
+{code}
+git --no-pager log origin/V7_9_1-branch --not V7_9_0 | grep -o '#[0-9]\+' | sort -u | sed 's/^.//' > all-tickets
+git --no-pager log origin/V7_9_1-branch --not V7_9_0 -- doc/ | grep -o '#[0-9]\+' | sort -u | sed 's/^.//' > doc-tickets
+diff -u doc-tickets all-tickets | grep '^+[0-9]'
+{endcode}
+The script above produces a list of tickets that have been incorporated into the 7.9.1 and that are not in 7.9.0, and that do not have commits under =doc/= As such, it also includes commits in 7.8.x and also commits that do not require version history. It is useful as a place to start with the version history preparation.
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.
