On 5/19/09 11:06 AM, Martijn Faassen wrote:
> Chris McDonough wrote:
> [snip]
>> Er, it actually isn't a major release.  None of *its* interfaces moved.  I
>> thought we were defining "major release" as "API change".
> Hm, a dependency change isn't a bugfix either.
> It's an edge case, and one where I think we should err on the side of
> caution. It's a change in behavior that could have more consequences
> than the normally bugfix, though less consequences than API change.
> It could be argued that a change in dependencies *is* a feature change.
> Less might be registered. People might depend on implicit dependencies
> being present (even though they shouldn't). Less might be monkey-patched...
> It was recorded here previously:
> http://docs.zope.org/zopetoolkit/steeringgroup/decisions.html
> "Moving code around as part of dependency refactoring is worth a feature
> release (x.y as opposed to x.y.z version number) for the affected
> packages. Changing an import to make use of a new package that came out
> of such refactoring is also worth a feature release."

OK, noted.


- C
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to