Not that my opinion about Dreamwidth development should hold much sway, but I'll give it anyway.
In all my development work, I usually use the next to last "stable" release of everything unless there is a particular added feature that I really want to use. No matter how long something stays in beta, I tend to find the edge case bug in new versions of languages. I prefer to let other people find it first. :)
Any opinion grounded in experience developing long-lived software (as yours appears to be) is worth considering.
The downside of your specific approach is that (if the Perl PTB stick to their once-a-year release cycle), we need to go through compatibility checks (and fixing) once per year, as opposed to every other year if we jumped to the latest version instead. OTOH, in addition to net getting to get hurt by the latest and greatest bugs that come with the latest and greatest version (as you mentioned), the incompatibilities between 2 successive versions are likely easier to deal with than if jumping 2 versions.
no subject
In all my development work, I usually use the next to last "stable" release of everything unless there is a particular added feature that I really want to use. No matter how long something stays in beta, I tend to find the edge case bug in new versions of languages. I prefer to let other people find it first. :)
no subject
The downside of your specific approach is that (if the Perl PTB stick to their once-a-year release cycle), we need to go through compatibility checks (and fixing) once per year, as opposed to every other year if we jumped to the latest version instead. OTOH, in addition to net getting to get hurt by the latest and greatest bugs that come with the latest and greatest version (as you mentioned), the incompatibilities between 2 successive versions are likely easier to deal with than if jumping 2 versions.