[Checkins] SVN: Sandbox/philikon/foundation/releasing-software.txt
Fix indentation (thanks Marius)
Philipp von Weitershausen
philikon at philikon.de
Fri Oct 5 05:07:40 EDT 2007
Log message for revision 80625:
Fix indentation (thanks Marius)
Changed:
U Sandbox/philikon/foundation/releasing-software.txt
-=-
Modified: Sandbox/philikon/foundation/releasing-software.txt
===================================================================
--- Sandbox/philikon/foundation/releasing-software.txt 2007-10-05 09:05:08 UTC (rev 80624)
+++ Sandbox/philikon/foundation/releasing-software.txt 2007-10-05 09:07:40 UTC (rev 80625)
@@ -40,30 +40,30 @@
as package data. Setuptools will only include them in the
distribution if they are checked into subversion.
- In the checkout of the tag perform the following steps:
+ In the checkout of the tag perform the following steps:
- a) Remove the "dev" marker from the version in ``setup.py``
+ a) Remove the "dev" marker from the version in ``setup.py``
- b) Commit these changes. It's acceptable that these changes modify
- the tag since they're purely related to release management.
+ b) Commit these changes. It's acceptable that these changes modify
+ the tag since they're purely related to release management.
- c) Create a distribution and upload it to PyPI using the following
- command::
+ c) Create a distribution and upload it to PyPI using the following
+ command::
- python setup.py register sdist upload
+ python setup.py register sdist upload
- If the package contains C extensions, you need to upload 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
+ python setup.py bdist_egg upload
- This may require the help from someone with a Windows
- installation and proper tools (Visual C).
+ 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
- versions and linking models (framework / non-framework).
+ 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
+ versions and linking models (framework / non-framework).
6. Back on the trunk or the release branch, increase the version
number in ``setup.py`` to the *next* release while preserving the
More information about the Checkins
mailing list