Re: [Zope3-dev] Re: Release process closure
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 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
Re: [Zope3-dev] Re: Release process closure
On Oct 4, 2007, at 9:25 AM, Baiju M wrote: Jim Fulton wrote: On Oct 4, 2007, at 6:51 AM, Philipp von Weitershausen wrote: > On 4 Oct 2007, at 00:59 , Jim Fulton wrote: >> On Oct 3, 2007, at 3:44 PM, 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 >>> >> >> Cool. I think you can delete 5b. You already update the date, >> as you should, on the trunk or branch. You want the actual >> release date to be part of the change log, so it has to be >> entered before making the tag. > > Done. > >> I think we need to split "d" into: >> >> d) "Create a source release" >> >> e) Test the source release. At a minimum, rerun the package tests >> using the source release. (I really need to add a buildout option >> to help with this.) > > So how would I do this? This feels a bit complicated: > > 1. Create a source distribution with:: > > $ python setup.py sdist > > 2. Extract the tarball:: > > $ tar xzf dist/foo.package-X.Y.tgz > > 3. Edit buildout.cfg to make the result of the tarball a develop > egg *instead* of the stuff in 'src':: > > [buildout] develop = foo.package-X.Y > > 4. Rerun the buildout:: > > $ bin/buildout > > 5. Run the tests:: > > $ bin/test No. :) Currently, you could: - Create the source distro. (Note that I always use sparkling clean Pythons, so the command you give doesn't work for me as setuptools isn't importable. I always use: bin/buildout setup . sdist Why you cannot install setuptools ? It's not that I cannot. I *will* not. I like my Python to be shiny sparkly clean. My Python is what I get after running configure, make, make-install. Period. My site- packages is empty. IMO, this is the only sane way to develop. Also, I get very very very cranky when someone wastes my time with a problem that is ultimately traced to crap installed in their Python that isn't part of a standard install. Very cranky. I'm feeling cranky just thinking about it. :) Jim -- Jim Fulton Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Release process closure
Jim Fulton wrote: On Oct 4, 2007, at 6:51 AM, Philipp von Weitershausen wrote: > On 4 Oct 2007, at 00:59 , Jim Fulton wrote: >> On Oct 3, 2007, at 3:44 PM, 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 >>> >> >> Cool. I think you can delete 5b. You already update the date, >> as you should, on the trunk or branch. You want the actual >> release date to be part of the change log, so it has to be >> entered before making the tag. > > Done. > >> I think we need to split "d" into: >> >> d) "Create a source release" >> >> e) Test the source release. At a minimum, rerun the package tests >> using the source release. (I really need to add a buildout option >> to help with this.) > > So how would I do this? This feels a bit complicated: > > 1. Create a source distribution with:: > > $ python setup.py sdist > > 2. Extract the tarball:: > > $ tar xzf dist/foo.package-X.Y.tgz > > 3. Edit buildout.cfg to make the result of the tarball a develop > egg *instead* of the stuff in 'src':: > > [buildout] develop = foo.package-X.Y > > 4. Rerun the buildout:: > > $ bin/buildout > > 5. Run the tests:: > > $ bin/test No. :) Currently, you could: - Create the source distro. (Note that I always use sparkling clean Pythons, so the command you give doesn't work for me as setuptools isn't importable. I always use: bin/buildout setup . sdist Why you cannot install setuptools ? Regards, Baiju M ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Release process closure
On Oct 4, 2007, at 6:51 AM, Philipp von Weitershausen wrote: On 4 Oct 2007, at 00:59 , Jim Fulton wrote: On Oct 3, 2007, at 3:44 PM, 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 Cool. I think you can delete 5b. You already update the date, as you should, on the trunk or branch. You want the actual release date to be part of the change log, so it has to be entered before making the tag. Done. I think we need to split "d" into: d) "Create a source release" e) Test the source release. At a minimum, rerun the package tests using the source release. (I really need to add a buildout option to help with this.) So how would I do this? This feels a bit complicated: 1. Create a source distribution with:: $ python setup.py sdist 2. Extract the tarball:: $ tar xzf dist/foo.package-X.Y.tgz 3. Edit buildout.cfg to make the result of the tarball a develop egg *instead* of the stuff in 'src':: [buildout] develop = foo.package-X.Y 4. Rerun the buildout:: $ bin/buildout 5. Run the tests:: $ bin/test No. :) Currently, you could: - Create the source distro. (Note that I always use sparkling clean Pythons, so the command you give doesn't work for me as setuptools isn't importable. I always use: bin/buildout setup . sdist - Add your dist directory to the list of find links - Specify the new version in your requirements - remove the develop entry - run the buildout - run the tests As I said, buildout could automate this in the future. Jim -- Jim Fulton Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Release process closure
On 4 Oct 2007, at 00:59 , Jim Fulton wrote: On Oct 3, 2007, at 3:44 PM, 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 Cool. I think you can delete 5b. You already update the date, as you should, on the trunk or branch. You want the actual release date to be part of the change log, so it has to be entered before making the tag. Done. I think we need to split "d" into: d) "Create a source release" e) Test the source release. At a minimum, rerun the package tests using the source release. (I really need to add a buildout option to help with this.) So how would I do this? This feels a bit complicated: 1. Create a source distribution with:: $ python setup.py sdist 2. Extract the tarball:: $ tar xzf dist/foo.package-X.Y.tgz 3. Edit buildout.cfg to make the result of the tarball a develop egg *instead* of the stuff in 'src':: [buildout] develop = foo.package-X.Y 4. Rerun the buildout:: $ bin/buildout 5. Run the tests:: $ bin/test f) If the package has extensions, make and test a windows egg. (You may need to get someone with the needed Windows tools to help you with this. :) f) Upload the release(s) to PyPI ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: Release process closure
On Oct 3, 2007, at 3:44 PM, 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 Cool. I think you can delete 5b. You already update the date, as you should, on the trunk or branch. You want the actual release date to be part of the change log, so it has to be entered before making the tag. I think we need to split "d" into: d) "Create a source release" e) Test the source release. At a minimum, rerun the package tests using the source release. (I really need to add a buildout option to help with this.) f) If the package has extensions, make and test a windows egg. (You may need to get someone with the needed Windows tools to help you with this. :) f) Upload the release(s) to PyPI Jim -- Jim Fulton Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
