docs/devinfo: update release info

Signed-off-by: Brian Paul <brianp@vmware.com>

docs/devinfo.html

@@ -163,36 +163,33 @@ branch is relevant.
 
 
 <h3>Verify and update version info</h3>
-<p>
-Create/edit the docs/relnotes-x.y.html file to document what's new in the release.
-Add the new relnotes-x.y.html file to <a href="relnotes.html">relnotes.html</a>.
-</p>
 
-<p>
-Update the MESA_MAJOR, MESA_MINOR and MESA_TINY version numbers in
-configs/default.
-Also update the VERSION line in the top-level Makefile.
-</p>
-
-<p>
-Make sure the values in src/mesa/main/version.h are correct.
-</p>
-
-<p>
-Update docs/news.html.
-</p>
+<dl>
+  <dt>configs/default</dt>
+  <dd>MESA_MAJOR, MESA_MINOR and MESA_TINY</dd>
+  <dt>Makefile.am</dt>
+  <dd>PACKAGE_VERSION</dd>
+  <dt>autoconf.ac</dt>
+  <dd>AC_INIT</dd>
+  <dt>src/mesa/main/version.h</dt>
+  <dd>MESA_MAJOR, MESA_MINOR, MESA_PATCH and MESA_VERSION_STRING</dd>
+</dl>
 
 <p>
 Create a docs/relnotes-x.y.z.html file.
 The bin/shortlog_mesa.sh script can be used to create a HTML-formatted list
 of changes to include in the file.
-Link the new docs/relnotes-x.y.z.html file into the main relnotes.html file.
+Link the new docs/relnotes-x.y.z.html file into the main <a href="relnotes.html">relnotes.html</a> file.
 </p>
 
 <p>
-Tag the files with the release name (in the form <b>mesa_X_Y</b>)
-with: <code>git tag -a mesa_X_Y</code>
-Then: <code>git push origin mesa_X_Y</code>
+Update <a href="news.html">docs/news.html</a>.
+</p>
+
+<p>
+Tag the files with the release name (in the form <b>mesa-x.y</b>)
+with: <code>git tag -a mesa-x.y</code>
+Then: <code>git push origin mesa-x.y</code>
 </p>
 
 
@@ -206,7 +203,7 @@ Make the distribution files.  From inside the Mesa directory:
 <p>
 After the tarballs are created, the md5 checksums for the files will
 be computed.
-Add them to the docs/relnotes-X.Y.html file.
+Add them to the docs/relnotes-x.y.html file.
 </p>
 
 <p>