Front page | perl.perl5.porters |
Postings from June 2015
On Fri, Jun 5, 2015 at 11:58 AM, Rocco Caputo <rcaputo@pobox.com> wrote: > > On Jun 5, 2015, at 11:42, Smylers <Smylers@stripey.com> wrote: > > > > Scenarios we may wish to support include: > > > > • Cautious Upgrader: Tallulah has a large warning-free codebase running > > under Perl 5.22. When she upgrades to 5.24 she doesn't want any > > additional warnings. > > I believe the sense of Cautious and Reckless are reversed here. > > Goofus is gong to slam a Perl upgrade into production without testing. > He won't want any newfangled warnings breaking his mission critical > applications, even indirectly by filling the logging partition, which > apparently isn't being monitored for sufficient free space. > > > • Reckless Upgrader: When Charley upgrades he wants his code to warn > > about all possible issues, including those that previous versions > > didn't warn about. > > Gallant wants new versions of Perl to tell him when his old code may > behave differently Deprecation warnings are always on by default. I don't think anyone wants this to change. > , or even have been subtly broken in ways that weren't > formerly detected. At the very least, he'll deploy to staging so he can > isolate and fix any new problems before the upgrade can break production. > > -- > Rocco Caputo <rcaputo@pobox.com> > >Thread Previous | Thread Next