[pytest-dev] 2.8.0 release plan? 2.7.2?

[Tibor Arpas]

How about the new hook call system vs the old __multicall__ ? Is the plan
still to deprecate the old way in 2.8 and remove in 2.9?

Any idea how many plugin-s use it and will brake (or were already updated)?

Tibor

On Thu, Jun 18, 2015 at 7:47 AM, holger krekel <holger at merlinux.eu> wrote:

> On Wed, Jun 17, 2015 at 22:06 -0700, Floris Bruynooghe wrote:
> > On 17 June 2015 at 05:31, Bruno Oliveira <nicoddemus at gmail.com> wrote:
> > > Hi, Do we have an idea of when we would like have a 2.8.0 release, or
> at
> > > least what we would like to see in the new version?
> >
> > Nope, maybe the pluggy dependency?  But not sure if that was the plan.
>
> FWIW I consider to vendor the pluggy dependency before pytest-2.8 is
> released.
> The main issue is that as projects start using pluggy indepdently of pytest
> there might be version conflicts when pluggy gets new releases, making
> it hard to test pluggy-using projects with pytest.
>
> > > And about 2.7.2?
> >
> > I think we should release that as soon as the python 3.5 compatibility
> > is sorted.  I'm on holiday for a few days though so won't get to look
> > at this again until mid-next week (but don't let that stop someone
> > else ;-)).
> >
> > I think Ronny had some 2.7.2 plans as well or wanted it soon for some
> reason?
> >
> > > I see
> > > there are a couple of fixes that are in master but should be
> backported to
> > > pytest-2.7 branch before making a 2.7.2 release.
> >
> > Hmm, if they where fixes I guess they should have gone to 2.7 right
> > away.  Sometimes the line is a bit blurry though.  It obviously
> > doesn't matter much if 2.8 overtakes 2.7.2, so if there's nothing
> > important that needs to happen for 2.8 then that would be fine too.
>
> Maybe we can just aim for pytest-2.8 in the next two weeks and forget
> about pytest-2.7.2 and then see to have more clarity regarding PR targets.
> Would it make sense to consider "master" to become the new "bug fix branch"
> and have a "pytest-2.9" then where we collect new features? This way
> the default is to do bugfixes which might be easier for newcomers to
> the project.
>
> best,
> holger
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20150618/ee740c12/attachment-0001.html>