Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-16 Thread Martijn Faassen
Hey, Stephan Richter wrote: [snip] -1 from me too. Having the previous version avoids having to look it up in CHANGES.txt or the tags, which is really lame if you do lots of releasing. From private conversations here at the Grok sprint with Christian I think that means that the steering

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-16 Thread Martijn Faassen
Hi there, Unless you think you have a great argument that you think will make significant portions of the ZTK steering group change their mind on this, this discussion should now be closed. We're sticking with our current release policy for the ZTK packages. This doesn't affect non-ZTK

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-15 Thread Reinout van Rees
On 2009-09-11, Benji York be...@zope.com wrote: On Fri, Sep 11, 2009 at 10:41 AM, Jim Fulton j...@zope.com wrote: On Fri, Sep 11, 2009 at 10:11 AM, Martijn Faassen faas...@startifact.com wrote: * I (and others) use tools to do releases (zest.releaser in my case). These tools are based on this

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-15 Thread Reinout van Rees
On 2009-09-11, Martijn Faassen faas...@startifact.com wrote: Jim Fulton wrote: but if it is, I propose to using 0 instead of the dev of the next version. Where I've used '0', I've found it to be less error prone. Ir also requires less effort because it means you never have to edit the

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-15 Thread Stephan Richter
On Tuesday 15 September 2009, Reinout van Rees wrote: On 2009-09-11, Martijn Faassen faas...@startifact.com wrote: Jim Fulton wrote: but if it is, I propose to using 0 instead of the dev of the next version. Where I've used '0', I've found it to be less error prone. Ir also requires

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-15 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Tuesday 15 September 2009, Reinout van Rees wrote: On 2009-09-11, Martijn Faassen faas...@startifact.com wrote: Jim Fulton wrote: but if it is, I propose to using 0 instead of the dev of the next version. Where I've

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-15 Thread Benji York
On Tue, Sep 15, 2009 at 4:56 PM, Tres Seaver tsea...@palladion.com wrote: I *like* the property of the 0 strategy that it makes the job of releasing a package a little harder:  releaseing software should be a thoughtful, careful process, not something you do without a bit of hesitation and

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-15 Thread Reinout van Rees
On 2009-09-15, Tres Seaver tsea...@palladion.com wrote: If you are making releases without having the CHANGES.txt open in your browser, then you need to put down the keyboard and back away slowly, so that nobody gets hurt. Reviewing / correcting the changelog (and comparing it with a diff

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-15 Thread Roger Ineichen
Hi Betreff: Re: [Zope-dev] official release policy ZTK is still not changed -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stephan Richter wrote: On Tuesday 15 September 2009, Reinout van Rees wrote: On 2009-09-11, Martijn Faassen faas...@startifact.com wrote: Jim Fulton wrote

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-11 Thread Jim Fulton
On Fri, Sep 11, 2009 at 8:55 AM, Martijn Faassen faas...@startifact.com wrote: Hi there, Apparently some people are using '0' instead of the next version for packages in the ZTK. Please do not do this for ZTK packages. The official policy for releasing is here.

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-11 Thread Martijn Faassen
Hey, Jim Fulton wrote: On Fri, Sep 11, 2009 at 8:55 AM, Martijn Faassen faas...@startifact.com wrote: Hi there, Apparently some people are using '0' instead of the next version for packages in the ZTK. Please do not do this for ZTK packages. The official policy for releasing is here.

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-11 Thread Jim Fulton
On Fri, Sep 11, 2009 at 10:11 AM, Martijn Faassen faas...@startifact.com wrote: Hey, Jim Fulton wrote: On Fri, Sep 11, 2009 at 8:55 AM, Martijn Faassen faas...@startifact.com wrote: Hi there, Apparently some people are using '0' instead of the next version for packages in the ZTK.

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-11 Thread Benji York
On Fri, Sep 11, 2009 at 10:41 AM, Jim Fulton j...@zope.com wrote: On Fri, Sep 11, 2009 at 10:11 AM, Martijn Faassen faas...@startifact.com wrote: * I (and others) use tools to do releases (zest.releaser in my case). These tools are based on this policy. Changing the policy breaks the tools.

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-11 Thread Martijn Faassen
Jim Fulton wrote: * it breaks dependencies on development versions which have version requirements in it (see Wichert's comments on the original thread). I'm not sure I understand this. I think your answer is below, and your solution would be to add a == 0 to the dependencies. We're

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-11 Thread Jim Fulton
I'm guilty of causing most these packages to violate the standards, while making their tests pass. Jim On Fri, Sep 11, 2009 at 11:39 AM, Martijn Faassen faas...@startifact.com wrote: Hi there, I was doing some thrawling of ZTK packages anyway, and this was easy. So,  it appears the following

Re: [Zope-dev] official release policy ZTK is still not changed

2009-09-11 Thread Martijn Faassen
Jim Fulton wrote: I'm guilty of causing most these packages to violate the standards, while making their tests pass. Wasn't my intent to track down the guilty, just ran into this information and wanted to record it for posterity. Making their tests pass is of course way more important than