in reply to Is maintaining multiple versions of a CPAN module a terrible idea?
I have been thinking about such things myself for post-1.000000 Type::Tiny. My planned approach is this:
Once 1.000000 is released, further 1.000xxx versions will be bugfixes with no new features.
While the 1.000xxx are being maintained as the main stable branch, I'll also be releasing 1.001_xxx versions with new features.
Because of the underscore in the 1.001_xxx version numbers, PAUSE won't index them. They are developer releases only.
Once 1.001_xxx has become stable, it will be released as 1.002000.
Once 1.002000 is released, further 1.002xxx versions will be bugfixes with no new features.
The 1.000xxx versions will still be on CPAN if anybody needs them. If any major bugs (e.g. security issues) come to light should be possible to upload a new 1.000xxx release, but it won't be indexed because there's already a newer version on CPAN.
While the 1.002xxx are being maintained as the main stable branch, I'll also be releasing 1.003_xxx versions with new features.
... etc...
A wiki page can exist, with links to download tarballs of the latest releases in the 1.000xxx, 1.002xxx, etc branches.