Version bump question? Bikeshed here.
I updated zc.receipe.testrunner to use zope.testrunner instead of zope.testing.testrunner. Initial testing has shown that this should be compatible, and although the code changes are minor, it's potentially unexpected. So should we release it as 2.0.0 or 1.3.0? 2.0.0 seems too radical to me, but then again I often say to others to not be afraid of version numbers. :) Opinions? -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
On Fri, Apr 30, 2010 at 9:54 PM, Lennart Regebro <regebro@gmail.com> wrote:
I updated zc.receipe.testrunner to use zope.testrunner instead of zope.testing.testrunner. Initial testing has shown that this should be compatible, and although the code changes are minor, it's potentially unexpected. So should we release it as 2.0.0 or 1.3.0?
If it is intended to be backwards compatible and seems to be so, I'd say go with 1.3. It sounds like a new package dependency, like we have had many others in minor releases. Hanno
On Fri, Apr 30, 2010 at 3:57 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
If it is intended to be backwards compatible and seems to be so, I'd say go with 1.3. It sounds like a new package dependency, like we have had many others in minor releases.
Since when were new dependencies not considered features? -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller
On Fri, Apr 30, 2010 at 10:03 PM, Fred Drake <fdrake@gmail.com> wrote:
On Fri, Apr 30, 2010 at 3:57 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
If it is intended to be backwards compatible and seems to be so, I'd say go with 1.3. It sounds like a new package dependency, like we have had many others in minor releases.
Since when were new dependencies not considered features?
They are of course. In my vocabulary a version consists of major. minor . micro (or patchlevel). Going from 1.2 to 2.0 is a major new feature release. Going from 1.2 to 1.3 is a minor new feature release. Package dependencies are a new feature and need a new feature release. They cannot be done in "third-dot" or "bug fix" releases. But Lennart didn't ask for that. Hanno
On Fri, Apr 30, 2010 at 4:10 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
Going from 1.2 to 1.3 is a minor new feature release.
Ok, if we're talking about changing the second number, this is fine. The wording "in a minor release" didn't connote "between minor releases" for me; I recognize I may just be a little pedantic on that point, though. -Fred -- Fred L. Drake, Jr. <fdrake at gmail.com> "Chaos is the score upon which reality is written." --Henry Miller
On Fri, Apr 30, 2010 at 22:26, Fred Drake <fdrake@gmail.com> wrote:
On Fri, Apr 30, 2010 at 4:10 PM, Hanno Schlichting <hanno@hannosch.eu> wrote:
Going from 1.2 to 1.3 is a minor new feature release.
Ok, if we're talking about changing the second number, this is fine.
The wording "in a minor release" didn't connote "between minor releases" for me; I recognize I may just be a little pedantic on that point, though.
That was a short bikeshedding. :) Anyway, 1.3.0 it is, then. -- Lennart Regebro: Python, Zope, Plone, Grok http://regebro.wordpress.com/ +33 661 58 14 64
participants (3)
-
Fred Drake -
Hanno Schlichting -
Lennart Regebro