Hi Ronny, > we should start to have a lifecycle that can start with cancel-able experiments,
We could elaborate better what an "experimental" status means in practice, like how we formalized deprecations in our backward compatibility policy. []s, On Mon, Jul 10, 2017 at 7:48 PM Ronny Pfannschmidt <[email protected]> wrote: > Hi everyone, > > each of those projects shouldn't just have a deprecation roadmap, > broken features we cant kill easily (like pytest's first throw at a > warning system) > are a minefield starting with their induction > > we should start to have a lifecycle that can start with cancel-able > experiments, > simply because we are a small group of volunteers that cant run internal > a/b testing on whether an api/idea is good in the long run - we need real > world feedback of early adopters in a fashion that allows us to cancel bad > things instead of keeping them "forever" > > -- Ronny > > Am 10.07.2017 um 18:30 schrieb Bruno Oliveira: > > Hey Tyler, > > Hmmm my initial gut feeling is to keep them separate. > > Also I'm not sure if it makes sense for pluggy given that it is not even > in 1.0 yet. What do others think? > > Cheers, > Bruno. > > On Mon, Jul 10, 2017 at 12:34 PM Tyler Goodlet <[email protected]> wrote: > >> Hey Bruno, >> >> Is it ok if I stick on stuff from pluggy (eg. __multicall__ support) or >> would you prefer I create a similar page for that in the pluggy wiki? >> >> Thanks. >> >> - Tyler >> > > > _______________________________________________ > pytest-dev mailing > [email protected]https://mail.python.org/mailman/listinfo/pytest-dev > > >
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
