On 2013-12-3 17:53 , David E. Wheeler wrote: >> The problem with this is that 'new perls' means 'not >> backwards-compatible language changes' which is a problem for people >> with existing code written to work with 'old perls'.
Very often, people stuck with "old perls" are also stuck with "old OS", "old postgres", "old dbdpg", old everything. I don't see a reason to hold back for those who are stuck in prehistoric ages. perl 5.12 (over 3.5 years old now) sounds like a fine baseline, especially when introducing possibly incompatible changes. We might consider doing emergency updates to older versions eg in case of security issues... (now, let me get back to phasing out my FreeBSD 4.11 servers! Argh!) -- Jan-Pieter Cornet "If you're doing nothing wrong, you have nothing to hide from the giant surveillance apparatus the government's been hiding." -- Stephen Colbert
signature.asc
Description: OpenPGP digital signature
