Isn't it just as bad to keep versions locked for months and years so we don't upset the delicate balance of versions on the production env? I've worked at a pl

Isn't it just as bad to keep versions locked for months and years so we don't upset the delicate balance of versions on the production env? I've worked at a place where they were running PHP 4.4.9 until about 8 months ago. And they were upgrading to 5.4! I get that it was work to convert a lot of the older code base to 5.4, but it was already passed EOL when they were switching to it. And 5.5 wasn't much behind it. So now in the near future, they'll need to upgrade again (though they probably wont), and they'll probably jump to 5.6, which EOLs in two years (probably two years after it EOLs).