[pytest-dev] preparing a breaking internal change - splitting Session into the node and the plugin

[Bruno Oliveira]

Hi everyone,

On Fri, Mar 9, 2018 at 10:46 AM RonnyPfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

>
> > I wouldn't take a major release to cram in as much changes as possible.
> > IMHO it's fine to have a major release for just one breaking change.
> > That way it's easier to manage possible fallout and build confidence
> > that major releases aren't *that* bad. The possibility of proper
> > deprecations trumps the wish to clean up as much as possible in one go.
> > Frequent small steps are better than big steps every once in a while.
> > The goal will be the same, but with less disruption.
>
> really good point, this reminds me of the way setuptools handles things
> - each major release only handles one singular point, which in turn
> ensures smooth transitions
>

Good idea, +1 to introduce just one major change during each major release.

Cheers,
Bruno.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20180316/4b56542f/attachment-0001.html>