On Wed, Oct 03, 2007 at 09:44:21PM +0200, Philipp von Weitershausen wrote: > Jim Fulton wrote: >> I'd really like to get to closure on the current approved release process. >> Philipp, would you mind separating the release process into a separate >> file? Or do you mind if I do it? > > Done: > http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/releasing-software.txt
Isn't step 4 redundant? I assume "the changelog" refers to CHANGES.txt in step 2: 2. Update the changelog to note the release date. Make sure the changelog is complete. <...> 4. Fill in the release date in ``CHANGES.txt``. Step 6.3: "python setup.py register sdist upload", should we assume that everyone will have a fixed version of setuptools installed, or should we recommend that people making the sdist on Windows system force the package format to tar.gz to avoid the unpleasantness with \r\n line endings in SOURCES.txt causing some files to not get extracted on POSIX systems? Purely formatting matter: the indentation of step 6 is inconsistent: 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 <snip indented list here> In the checkout of the tag perform the following steps: <...> Also, there are two steps numbered 6: 6. Back on the trunk or the release branch, increase the version number in ``setup.py`` to the *next* release while preserving the <...> Marius Gedminas -- Never attribute to malloc that which can be adequately explained by stupidity. -- From the .sig of [EMAIL PROTECTED] (Joerg Pommnitz)
signature.asc
Description: Digital signature
_______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com