[Checkins] SVN: Sandbox/philikon/foundation/releasing-software.txt Incorporate some more comments from Jim

[Philipp von Weitershausen]

Log message for revision 80600:
  Incorporate some more comments from Jim
  

Changed:
  U   Sandbox/philikon/foundation/releasing-software.txt

-=-
Modified: Sandbox/philikon/foundation/releasing-software.txt
===================================================================
--- Sandbox/philikon/foundation/releasing-software.txt	2007-10-04 10:50:30 UTC (rev 80599)
+++ Sandbox/philikon/foundation/releasing-software.txt	2007-10-04 10:51:15 UTC (rev 80600)
@@ -24,9 +24,11 @@
    render the long description nicely.  It will treat it as plain text
    instead.
 
-4. Create a release tag.
+4. Fill in the release date in ``CHANGES.txt``.
 
-5. Get a separate checkout of the release tag for creating the
+5. Create a release tag.
+
+6. Get a separate checkout of the release tag for creating the
    distribution tarball and eggs.  It is important that you don't do
    this on the trunk or release branch to avoid
 
@@ -44,22 +46,22 @@
 
   a) Remove the "dev" marker from the version in ``setup.py``
 
-  b) Fill in the release date in ``CHANGES.txt``.
-
-  c) Commit these changes.  It's acceptable that these changes modify
+  b) Commit these changes.  It's acceptable that these changes modify
      the tag since they're purely related to release management.
 
-  d) Create a distribution and upload it to PyPI using the following
+  c) Create a distribution and upload it to PyPI using the following
      command::
 
        python setup.py register sdist upload
 
-     If the package contains C extensions and you have access to a
-     Windows machine with a Visual C compiler installed, you should
-     consider uploading a binary Windows egg as well::
+     If the package contains C extensions, you need to upload a binary
+     Windows egg as well::
 
        python setup.py bdist_egg upload
 
+     This may require the help from someone with a Windows
+     installation and proper tools (Visual C).
+
      Binary eggs for Linux or MacOSX should **never** be uploaded
      because those platforms vary too much to be binary-compatible
      with each other, due to varying UCS support, different libc
@@ -78,12 +80,11 @@
          ...
          )
 
-   In ``CHANGES.txt``, fill in the release date of the just released
-   version (you did this on the tag in step 5b) and add a *new*
-   section for the upcoming release.  The release date for that should
-   say "unreleased" so that committers recording their changes won't
-   accidentally put their entry in the section for an already released
-   version.  For example::
+   In ``CHANGES.txt`` add a *new* section for the upcoming release.
+   The release date for that should say "unreleased" so that
+   committers recording their changes won't accidentally put their
+   entry in the section for an already released version.  For
+   example::
 
      3.4.2 (unreleased)
      ------------------