Heh, even after the discussion on the poll proposal, I still don't know what the right answer is for me.

I gave it a deeper review this time. Out of my 30 CPAN modules

• Undeclared - 16x
• 5.6 - 2x (because they extend Log::Any, which requires 5.6)
• 5.8 - 4x (usually due to Scalar::Util::weaken, or some kind of unicode reason)
• 5.10 - 3x (endian pack, or // in a hot path)
• 5.14 - 3x (all part of the same ecosystem, and I don't remember why!)
• 5.20 - 1x (my sub was crucial to the design)
• 5.36 - 1x (it's a web app, not a module you'd depend on, so just run the latest perl in a container if you need to)

For the undeclared majority, I leave them undeclared because I want CPAN Testers to find out the minimum version for me. Next time I'm adding a feature, I check testers to see if there's an obvious change I can make to extend compatibility. A majority of these modules now support back to 5.8, and a few even handle 5.6, or maybe even earlier because that's where cpan testers stops, and I've never had a working copy of 5.5 or earlier. Some, I don't even know, because they depend on special C libraries that aren't available on most smoke testers, but I probably tested them locally with 5.8 or 5.10, depending whether I was developing on my laptop or desktop. (I couldn't get perlbrew 5.8 to install on my laptop for reasons I never tracked down)

I answered 5.8 in the poll because that's where I stop caring.