[pytest-dev] Postpone 3.0?

[Oliver Bestwalter]

Hi all,

I just opened a PR adding the docs about our backwards compatibility
policy: https://github.com/pytest-dev/pytest/pull/1736

With that PR all necessary elements are in place as discussed (internal
pytest warnings on by default, possibility to silence these warnings,
documentation explaining the policy).

I created it against the features branch as I am not sure if the
documentation restructuring will make it into 3.0

Cheers
Oliver

On Fri, 15 Jul 2016 at 18:06 Florian Bruhin <me at the-compiler.org> wrote:

> * Floris Bruynooghe <flub at devork.be> [2016-07-15 15:29:18 +0100]:
> > On 14 July 2016 at 23:45, Brianna Laugher <brianna.laugher at gmail.com>
> wrote:
> > > It's mainly Floris, Oliver and me that are the hold up right? Removing
> > > reinterpret assert and 2x docs.
> >
> > Reinterpret is now removed as of this morning!  I should do one more
> > PR with some doc updates.  Is that fine to do against current docs in
> > the repo for the doc-reorg?
> >
> > The milestone (https://github.com/pytest-dev/pytest/milestone/2) has a
> > lot of things still outstanding.  I'm happy to postpone, we could aim
> > for the end of the EuroPython sprints?  (although I won't be around
> > for that weekend)  Or maybe a week later even as sprints probably
> > introduce some instability.  So I'd say aim for 1st August maybe?
>
> I think I've mentioned it in the past: We should postpone anything
> which is not a breaking change to 3.1, we have more than enough
> awesome stuff for 3.0 already.
>
> I think nobody took a look at the issues - we have simple feature
> proposals from 2012 in there, sho, should they really block 3.0?
>
> Ronny, things like "Support for Python 3.4 unittest subtests" or "drop
> argparse" are marked as "critical" (mostly by you) - what's so
> critical about them? To me, critical would imply we can under no
> circumstances release 3.0 without that. "pytest deletes my project
> files" would be critical. Feature proposals (sometimes years old)
> really aren't...
>
> > Speaking of the EuroPython sprints, is anybody going to be there to
> > organise a py.test sprint?  Raphael might still be (but then he might
> > want to defect to cookiecutter), Florian as well not sure about
> > others?  Anyone want to volunteer leading a sprint?
>
>
> I'll be there on Saturday and maaaybe Sunday morning, but chances are
> I'm going to sprint on pylint again.
>
> Florian
>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
> >
> >
> > Floris
> > _______________________________________________
> > pytest-dev mailing list
> > pytest-dev at python.org
> > https://mail.python.org/mailman/listinfo/pytest-dev
> >
>
> --
> http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>          I love long mails! | http://email.is-not-s.ms/
> _______________________________________________
> 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/20160717/ab7fef10/attachment.html>