Hi Bruno, I’m happy with either, but I need to know as soon as possible as it’s only a week until my EuroPython talk.
Right now, I find it quite hard to work on my slides w/o knowing when pytest 3.0 is going to land and what it will include. Please don’t get me wrong. Again, anything works for me as long as I know a preliminary release date and scope as I want to prepare demos for the presentation. Cheers Raphael > On 14 Jul 2016, at 21:21, Bruno Oliveira <nicodde...@gmail.com> wrote: > > Hi pytesters, > > Our original target date for pytest 3.0 was around this week (just before > EuroPython), but it seems we are not going to make it as there are some > issues still in the 3.0 check list which have not been merged: > > https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist > <https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist> > > My question is if we should delay the release a little bit and give more time > to people to work on them for 3.0, or bite the bullet and make the release > anyway this weekend/early next week? And if we decide to delay, what people > think would be a good time for a new target date? > > Personally I would rather wait a little more because I consider the remaining > issues important to go in 3.0. > > Btw, I was taking a look at the Pulse page on GitHub > (https://github.com/pytest-dev/pytest/pulse > <https://github.com/pytest-dev/pytest/pulse/monthly>) and in the last 7 days > we have merged 16 PRs. That's awesome. :) > > Cheers, > Bruno. > > > _______________________________________________ > pytest-dev mailing list > pytest-dev@python.org > https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________ pytest-dev mailing list pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
