Version bump, pychecker fixes and installation-procedure tweaks.

1 files changed, 19 insertions, 16 deletions

diff --git a/www/hacking.html.in b/www/hacking.html.in
index 8f1fd484..76356644 100644
--- a/www/hacking.html.in
+++ b/www/hacking.html.in
@@ -1431,23 +1431,26 @@ will have a day or so to get their urgent fixes in.</dd>
 <dd>It will need to be modified in SConstruct.  Make sure the 'dev' 
 suffix is gone.</dd>
 
-<dt>5. Remove revision.h and rebuild leapseconds.cache.</dt>  
-<dd>First, remove revision.h so it will be rebuilt correctly
-for the tarball.  Then, rebuild the leap-second list
-used for rollover checks with 'scons leapseconds.cache' Note: The latter will
-require Internet access, and fail (leaving the existing leap-second
-list in place) if that is not available.</dd>
-
-<dt>6. Fix compiler and scan-build warnings.</dt>
+<dt>5. Remove revision.h (or just do <command>scons -c</command>)</dt>
+<dd>This step ensurered that the release ID in the revision.h that
+goes in the tarball will look right.</dd>
+
+<dt>6. Rebuild leapseconds.cache.</dt>  
+<dd>Rebuild the leap-second list used for rollover checks with 'scons
+leapseconds.cache' Note: The latter will require Internet access, and
+fail (leaving the existing leap-second list in place) if that is not
+available.</dd>
+
+<dt>7. Fix compiler and scan-build warnings.</dt>
 <dd>Look for compiler and <a
 href="http://devel.recluse.de/~bzed/scan-build/gpsd/">scan-build</a>
 warnings and fix them.</dd>
 
-<dt>7. Update the NEWS file</dt>
+<dt>8. Update the NEWS file</dt>
 <dd>Make sure the topmost entry in the changelog portion of
 gpsd.spec.in is up-to-date and properly timestamped.</dd>
 
-<dt>8. Run the regression tests and other checks</dt>
+<dt>9. Run the regression tests and other checks</dt>
 <dd>If it doesn't pass regressions, it isn't ready to ship.
 <ol>
 <li>scons testbuild</li>
@@ -1457,23 +1460,23 @@ gpsd.spec.in is up-to-date and properly timestamped.</dd>
 </ol>
 </dd>
 
-<dt>9.Perform a validation pass on the website content.</dt>
+<dt>10.Perform a validation pass on the website content.</dt>
 <dd>See the instructions near validation-list in the scons recipe.  
 Then upload the corrected pages with <code>scons website</code>.</dd>
 
-<dt>10. Ship to our hosting site</dt>
+<dt>11. Ship to our hosting site</dt>
 <dd>Make the tarball (<code>scons dist</code>), upload it to @SITENAME@,
 (<code>scons upload-release</code>), and notify the announce list.</dd>
 
-<dt>11. Tag the release in git</dt>
-<dd><p><code>scons tag-relese</code> will do it.</p></dd>
+<dt>12. Tag the release in git</dt>
+<dd><p><code>scons tag-release</code> will do it.</p></dd>
 
-<dt>12. Bump the release number and push that commit</dt>
+<dt>13. Bump the release number and push that commit</dt>
 <dd>Bump the release number in SConstruct, adding a '~dev' suffix
 so tarball instances pulled from the repo will be clearly
 distinguishable from the next public release.</dd>
 
-<dt>13. Announce the release</dt>
+<dt>14. Announce the release</dt>
 <dd>Announce the release, and the resumption of regular commits, on
 the dev list.</dd>
 </dl>