Assuming this was intended as a reply to my post rather than bulk88's.

With 5 months between major versions, that equates to a whole 10 (TEN) months before all a vendors efforts to ensure the distributed version of perl works with all the distributed packages and tools it supplies written in perl are obsolete. It isn't long enough.

It is no wonder that vendors (redhat et al) are choosing to stick with old versions. With Perl's major version changing twice (or 3 times) between vendors major releases, by the time they've frozen their distribution and taken it through their testing processes to a release, the Perl they included is not just out-of-date, it is out-of-official-support.

With the recent rates of turnover, there is never a period of stability long enough for them to get from code-freeze to release. And if they've got to stick with an out-of-support version, why wouldn't they stick with the one they know.

Or more likely, drop their dependency upon the unstable moving target that is Perl, throw in an old version as a token gesture, and move over to using Python.