[Zope3-dev] Re: Automated egg releases
Marius Gedminas wrote: People make mistakes. Can we reduce the number/severity of those mistakes by creating a Python script to automate the release process as much as possible? [snip] I'd be happy to work on such a script during the sprint, if someone could help me figure out what exactly it should to do. +10! Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Automated egg releases
Jim Fulton wrote: I'm not too keen on trying to automate this with a Python script. I suggest we start with a human script. I agree. I think Philipp has a start at this. Philipp, could you remind us where this is? http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt I suggest we review it and then post it prominately somewhere that people (I) can easily find it. Yes, that would be good. I I, for one, promise to read it every time I make a release until I've memorized it. It would be good if everybody could use it (as least the section on how to make releases) as a step-by-step procedure every time. I certainly do this now and as far as I remember, back in the one-big-tarball days, we all did using the MakingARelease wiki page. By the way, I'm planning on spelling out several more things: * That you should never ever delete a release, even if it's a brown bag release. * That setup.py sdist should be run from a **clean** checkout of the tag that you just created. That avoids - forgetting to tag or tagging the wrong thing (happened to me and others) - forgetting to clean up the 'build' directory (happened to me and my egg contained old stuff that shouldn't have been in there) - forgetting to check in files; setuptools will only include package data files that are in subversion (happened to me and other people) * That you should check if the long_description renders as proper reStructuredText before you update the PyPI page (reST errors will cause the rendering to be all messed up. Any other suggestions are highly welcome. -- http://worldcookery.com -- Professional Zope documentation and training ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Automated egg releases
On Wed, Sep 26, 2007 at 04:19:35PM +0200, Philipp von Weitershausen wrote: Any other suggestions are highly welcome. That problem with building eggs on Windows: if you need to pass some argument to setup.py sdist to get a tar.gz egg, please update http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt because it currently says just | * Upload the package to PyPI with the following command:: | | python setup.py register sdist upload Marius Gedminas -- Added mysterious, undocumented --scanflags and --fuzzy options. -- nmap 3.0 announcement 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
[Zope3-dev] Re: Automated egg releases
Jim Fulton wrote: I'm not too keen on trying to automate this with a Python script. I suggest we start with a human script. I think Philipp has a start at this. Philipp, could you remind us where this is? I suggest we review it and then post it prominately somewhere that people (I) can easily find it. I, for one, promise to read it every time I make a release until I've memorized it. I definitely think we should work out a human procedure *first*. But some tools to assist the human in doing repetitive, failure-prone work (releasing versions of many eggs) would definitely be appreciated by me. Perhaps these could be made lint-like initially. I.e. you run them and the tool reports possible problems (no tag created, version number in CHANGES.txt appears wrong, setup.py misses information we want in there, etc). Once that's in place, we could introduce features that actually perform actions. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Automated egg releases
Stephan Richter wrote: [snip] Doing another checkout of the tag will create a significant overhead to the release process of a package. I'd like to highlight this. We need to be careful we don't increase release overhead too much, otherwise it won't happen/people will make mistakes. Regards, Martijn ___ 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: Automated egg releases
On Sep 26, 2007, at 11:19 AM, Martijn Faassen wrote: Stephan Richter wrote: [snip] Doing another checkout of the tag will create a significant overhead to the release process of a package. I'd like to highlight this. We need to be careful we don't increase release overhead too much, otherwise it won't happen/people will make mistakes. +10 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: Automated egg releases
On Wed, Sep 26, 2007 at 05:19:45PM +0200, Martijn Faassen wrote: Stephan Richter wrote: [snip] Doing another checkout of the tag will create a significant overhead to the release process of a package. I'd like to highlight this. We need to be careful we don't increase release overhead too much, otherwise it won't happen/people will make mistakes. Reducing overhead is why I proposed an automated tool. To put it in perspective, I believe the proper sequence of things is 1. keep doing stuff so you learn (from mistakes and whatnot) what needs to be done 2. document the process because (1) you'll forget what you learned, and (2) other people won't know what you learned 3. automate, because following a long process by hand is boring, and bored people make mistakes. Marius Gedminas -- I would suggest re-naming rmbdd(). I _assume_ that dd stands for data dependent, but quite frankly, rmbdd looks like the standard IBM we lost every vowel ever invented kind of assembly lanaguage to me. -- Linus Torvalds 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: Automated egg releases
On 9/26/07, Marius Gedminas [EMAIL PROTECTED] wrote: Reducing overhead is why I proposed an automated tool. Exactly. I like this approach myself. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ 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: Automated egg releases
On Wed, 2007-09-26 at 17:18 +0200, Martijn Faassen wrote: I definitely think we should work out a human procedure *first*. But some tools to assist the human in doing repetitive, failure-prone work (releasing versions of many eggs) would definitely be appreciated by me. Perhaps these could be made lint-like initially. I.e. you run them and the tool reports possible problems (no tag created, version number in CHANGES.txt appears wrong, setup.py misses information we want in there, etc). Once that's in place, we could introduce features that actually perform actions. +100 An advisory tool could also optionally use Cheesecake. - Michael R. Bernstein signature.asc Description: This is a digitally signed message part ___ 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: Automated egg releases
Philipp von Weitershausen wrote at 2007-9-26 16:19 +0200: ... * That you should never ever delete a release, even if it's a brown bag release. But, if you know it is severely broken and you do not have a working replacement, you should remove it as soon as possible -- to avoid more people to get this broken state and allow them to usually get the previous working state instead. Mayby PyPI has a different solution to this then deleting the release? -- Dieter ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Automated egg releases
Dieter Maurer wrote: Philipp von Weitershausen wrote at 2007-9-26 16:19 +0200: ... * That you should never ever delete a release, even if it's a brown bag release. But, if you know it is severely broken and you do not have a working replacement, you should remove it as soon as possible -- to avoid more people to get this broken state and allow them to usually get the previous working state instead. Mayby PyPI has a different solution to this then deleting the release? The alternative is to upload a new release with a newer version number. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: Automated egg releases
Fred Drake wrote: On 9/26/07, Marius Gedminas [EMAIL PROTECTED] wrote: Reducing overhead is why I proposed an automated tool. Exactly. I like this approach myself. Sure, I support it too. That said, I'd still like the process *without* the tool comprehensible by normal human beings. The automation cannot be an reason to create a horrendously complicated release process, just because we can. I may change my mind on this after we've seen a tool work reliably for everybody for all use cases for a couple of years. :) Regards, Martijn ___ 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: Automated egg releases
On 9/26/07, Martijn Faassen [EMAIL PROTECTED] wrote: That said, I'd still like the process *without* the tool comprehensible by normal human beings. Agreed; I was trying to usurp the goal of having a reasonable process. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
