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:
-1: Check out a copy of the version history to verify:
-{code}
-git clone /p/condor/repository/CONDOR_DOC.git
-cd CONDOR_DOC
-git checkout -b V7_0_2-branch origin/V7_0_2-branch
-{endcode}
+1: The version history is in the =doc/= tree in the git reposictory.
Inside doc, you'll need to edit =version-history/X-Y.history.tex= where =X-Y= matches the release series you're working from (e.g. =7-0=).
1: Run git log between the last release and the current release from the same series:
{code}
@@ -24,7 +19,7 @@
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.
+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 does not catch commits that should have ticket numbers and do not. 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 HTCondor 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.
