*:: =cd /p/condor/public/html/manual=
 *:: =rm v7.0=
 *:: =ln -s v7.0.3 v7.0=
------
-  15. Update the web HTML regarding this release
-          * cvs -d /p/condor/repository/HTML co condor-web
-          * cd condor-web
-          * edit src/lib/news.mas (to add an announcement 'Whats New?')
-                o Here is a sample announcement:
 
+1: Update the web HTML regarding this release
+*:: =cvs -d /p/condor/repository/HTML co condor-web=
+*:: =cd condor-web=
+*:: edit =src/lib/news.mas= (to add an announcement 'Whats New?')
+*::: Here is a sample announcement:
+{code}
                       { date => 'January 22, 2008',
                         title => 'Condor 7.0.0 released!',
                   	  news => <<ENDNEWS
-                  The Condor Team is pleased to announce the release of
-                  Condor 7.0.0. This first release in a new stable series
-                  includes all new features added in the 6.9 development
-                  series.  See the
-                  <a href="http://www.cs.wisc.edu/condor/manual/v7.0/8_3Stable_Release.html#sec:New-7-0-0">Version
-                  History</a> for a complete list of changes.  Condor 7.0.0
-                  binaries and source code are available from
-                  <a href="http://www.cs.wisc.edu/condor/downloads/">our
-                  Downloads page.</a>
-                  ENDNEWS
+The Condor Team is pleased to announce the release of
+Condor 7.0.0. This first release in a new stable series
+includes all new features added in the 6.9 development
+series.  See the
+<a href="http://www.cs.wisc.edu/condor/manual/v7.0/8_3Stable_Release.html#sec:New-7-0-0">Version
+History</a> for a complete list of changes.  Condor 7.0.0
+binaries and source code are available from
+<a href="http://www.cs.wisc.edu/condor/downloads/">our
+Downloads page.</a>
+ENDNEWS
                   	},
+{endcode}
+*:: edit =src/downloads/index.html= (to fix the release-specific text on the main downloads page)
+*:: touch =src/index.html= (so the main page updates with the version information from the =downloads/index.html= page)
+*:: touch =src/manual/index.html= (so the manual links update with the version information from the =downloads/index.html= page)
+*:: NOTE: if you're doing the first release of a new release series, you'll also need to edit:
+*::: =src/index.html= to:
+*:::: change the "The Condor Manual:" list of links (chances are good you'll want to remove something older when you add the new one -- we'll never want that list to be longer than 3 links).
+*:::: Change where the links under Current Releases goes to. The text label for the link automatically updates, but the link doesn't.
+*::: =src/developers/index.html= to add the new series to the "Manuals and Other Documentation" list.
+*::: edit =src/manual/index.html= (to update which versions of each branch/release series are the current manual)
+*:: =cvs commit= (all of your changes in condor-web)
+*:: =./generate_html src= (to update the HTML on the web with your changes).
+
+1: {link: http://www.cs.wisc.edu/condor/developers/burn.html Archive} release products to DVD. Get recordable DVDs and DVD slipcovers from Ken. Drop off the finished DVD with Pete, who will store it in a box in his filing cabinet. Include the following (the archiving directions include these):
+*:: Binary tarballs. _This includes archiving the unstripped binaries._
+*:: Matching glidein tarballs. Get these from =/p/condor/public/binaries/glidein=.
+{code}
+$ ssh tonic "cd /p/condor/public/binaries; tar cf - glidein/7.1.3" | tar xvfpS -
+{endcode}
+*:: Source tarball.
+*:: Manual: tarball of HTML tree, and =ref.pdf=. The HTML files are in =/p/condor/public/html/manual=. Do something like this:
+{code}
+$ ssh tonic "cd /p/condor/public; tar cf - html/manual/v7.1.3" | tar xvfpS -
+$ ssh tonic "cd ; tar cf - doc" | tar xvfpS -
+{endcode}
+
+1: Send email to condor-world and condor-users. Here is a sample announcement:
+{code}
+Hello,
+
+The Condor Team is pleased to announce the release of Condor 7.0.0. This first
+release in a new stable series includes all new features added in the 6.9
+development series.  See the Version History for a complete list of changes.
+Condor 7.0.0 binaries and source code are available from our Downloads page.
 
-          * edit src/downloads/index.html (to fix the release-specific text on the main downloads page)
-          * touch src/index.html (so the main page updates with the version information from the downloads/index.html page)
-          * touch src/manual/index.html (so the manual links update with the version information from the downloads/index.html page)
-          * NOTE: if you're doing the first release of a new release series, you'll also need to edit:
-                o src/index.html to:
-                      + change the "The Condor Manual:" list of links (chances are good you'll want to remove something older when you add the new one -- we'll never want that list to be longer than 3 links).
-                      + Change where the links under Current Releases goes to. The text label for the link automatically updates, but the link doesn't.
-                o src/developers/index.html to add the new series to the "Manuals and Other Documentation" list.
-                o edit src/manual/index.html (to update which versions of each branch/release series are the current manual)
-          * cvs commit (all of your changes in condor-web)
-          * ./generate_html src (to update the HTML on the web with your changes).
-
-  16. Archive release products to DVD. Get recordable DVDs and DVD slipcovers from Ken. Drop off the finished DVD with Pete, who will store it in a box in his filing cabinet. Include the following (the archiving directions include these):
-          * Binary tarballs. This includes archiving the unstripped binaries.
-          * Matching glidein tarballs. Get these from /p/condor/public/binaries/glidein .
-
-            $ ssh tonic "cd /p/condor/public/binaries; tar cf - glidein/7.1.3" | tar xvfpS -
-
-
-          * Source tarball.
-          * Manual: tarball of HTML tree, and ref.pdf . The HTML files are in /p/condor/public/html/manual . Do something like this:
-
-            $ ssh tonic "cd /p/condor/public; tar cf - html/manual/v7.1.3" | tar xvfpS -
-            $ ssh tonic "cd ; tar cf - doc" | tar xvfpS -
-
-
-  17. Send email to condor-world and condor-users. Here is a sample announcement:
-
-      Hello,
-
-      The Condor Team is pleased to announce the release of Condor 7.0.0. This first
-      release in a new stable series includes all new features added in the 6.9
-      development series.  See the Version History for a complete list of changes.
-      Condor 7.0.0 binaries and source code are available from our Downloads page.
-
-      Version History:
+Version History:
         http://www.cs.wisc.edu/condor/manual/v7.0/8_3Stable_Release.html#sec:New-7-0-0
 
-      Downloads Page:
+Downloads Page:
         http://www.cs.wisc.edu/condor/downloads/
 
 
-      Thank you for your interest in Condor!
+Thank you for your interest in Condor!
+
+
+- The Condor Team
+{endcode}
 
+1: Close out all {link: http://pumori.cs.wisc.edu/cgi-bin/gnats/gnatsweb.pl Gnats} problem reports fixed by this release.
 
-      - The Condor Team
+1: Update the Condor wikipedia page to indicate the current stable release.
 
-  18. Close out all Gnats problem reports fixed by this release.
-  19. If this is a stable series, update the Condor wikipedia page to indicate the current stable release.
-  20. Stop building the branch nightly:
-          * cd /p/condor/home/tools/cvs-tools
-          * Edit create_build_tag-input
-          * Delete the section that defined the nightly build tag for this branch.
-          * cvs diff create_build_tag-input (to verify the change before you commit it)...
-          * cvs commit -m "added nightly build tags for V6_X_Y-branch" create_build_tag-input
+1: Stop building the branch nightly:
+*:: =cd /p/condor/home/tools/cvs-tools=
+*:: Edit =create_build_tag-input=
+*:: Delete the section that defined the nightly build tag for this branch.
+*:: =cvs diff create_build_tag-input= (to verify the change before you commit it)...
+*:: =cvs commit -m "added nightly build tags for V6_X_Y-branch" create_build_tag-input=