Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I don't think chromatic is proposing that Perl start break back compat willy nilly. He's been quite clear that he wants to see Perl on a time-based release cycle with published deprecation schedules.

    Imagine if Perl release 4 times a year. Then if there was a desire to deprecate something, a release could say "feature X will be removed after 6 more releases, 18 months from now".

    That seems pretty reasonable.

    Furthermore, no one out there is jumping from 5.6 to 5.10 without some serious testing. Even with Perl'

    • One problem with this approach as being a "viable" upgrade cycle for deprecations is that you and I might upgrade regularly, incrementally and pay lots of attention to point releases, but businesses generally don't. They stay at 5.6.1 for many years and then gird themselves for a jump to 5.8.8. Thus, your nifty "four releases a year" means nothing to them. They don't dare upgrade their perl in parallel with those four releases (that would be very foolish of them), but they wait too long between releases (for the same reason they delay some developers paying back technical debt).

      I'm not arguing for or against this behavior on the part of many businesses (but it's not as insane as people think), but it's pretty common behavior in most businesses I've either worked at or consulted at. "18 months from now" means nothing to them.

      • But those people will have the same problems with regular releases as they have now. Jumping from 5.6.1 to 5.8.8 (or 5.10.0) is a big deal with the current release system. If there were time-based releases, jumping across a huge number of releases will _still_ be a big deal.

        In both cases, you'll have to test all your code very carefully. You may also just give up and not upgrade.

        I've heard about Morgan Stanley's environment where the basically have apps deployed on every single version of Perl, and each app