> On Mar 6, 2017, at 13:17, Jonathan Vanasco <[email protected]> wrote: > > Yes, it is a giant pain. That's why I wanted to warn people explicitly in > this case because I don't want anyone suffering dataloss because their > transaction manager changed. > > That's why I brought this up - this is a bit more of a 'dangerous' API change. > > People following best-practices won't be affected, but people who don't > follow them will be -- and they're likely to flood here+github+stack-overflow > with bug reports. (at least that's what I've seen in the past). > > To minimize that, i've seen projects switch names or implement some sort of > affirmative consent by purposefully breaking the API. > > What Mikko said is true when everybody does the right thing -- unfortunately > most people don’t.
Then we’ll deal with the posts and questions when they come up… it’s not that big of a problem. -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/pylons-discuss/527D334D-AB17-4E43-A803-02DDF524113D%400x58.com. For more options, visit https://groups.google.com/d/optout.
