*resent after bad email client config* i like the 3.2 plan,
i think its fine to mark 3.1 as botched we should have a proper discussion about feature lifetimes in future, just deprecation is simply not enough - and it seems we repeat mishaps around releasing "complete" features -- Ronny Am 29.05.2017 um 14:06 schrieb Bruno Oliveira: > Hi Floris and Brian, thanks for joining. > > On Mon, May 29, 2017 at 8:44 AM Floris Bruynooghe <[email protected] > <mailto:[email protected]>> wrote: > > Hi, > > On 26 May 2017 at 15:51, Brian Okken <[email protected] > <mailto:[email protected]>> wrote: > > My opinion: > > - make 3.1.1 with this feature opt in > > I'd have agreed with this initially. But I think releasing an > un-broken version should probably only be done within the first > 24-48h. After that the pain might just increase rather then decrease. > > > If we were to make it opt-in, I would rather release a 3.2.0 version; > this way we can think of 3.1 as a "botched" release and more > emphatically communicate the change to users. > > > - new features that change behavior in backwards incompatible > way should be > > opt in. > > Probably with a note that next major release they'll be switched on by > default and give people the time to already disable them in their > config for that case > > > Sounds like a good idea. The problem in this case was that we didn't > foresee stuff actually breaking, otherwise it would be an opt-in > feature from the start. > > Guys, anymore opinions? I'm willing to prepare a 3.2.0 release today > with warnings opt-in if we all agree this is the best course of action. > > Cheers, > Bruno. > > > _______________________________________________ > pytest-dev mailing list > [email protected] > https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________ pytest-dev mailing list [email protected] https://mail.python.org/mailman/listinfo/pytest-dev
