note
tobyink
<p>I have been thinking about such things myself for post-1.000000 [mod://Type::Tiny]. My planned approach is this:</p>
<ul>
<li><p>Once 1.000000 is released, further 1.000xxx versions will be bugfixes with no new features.</p></li>
<li><p>While the 1.000xxx are being maintained as the main stable branch, I'll also be releasing 1.001_xxx versions with new features.</p>
<p>Because of the underscore in the 1.001_xxx version numbers, PAUSE won't index them. They are developer releases only.</p></li>
<li><p>Once 1.001_xxx has become stable, it will be released as 1.002000.</p>
<p>Once 1.002000 is released, further 1.002xxx versions will be bugfixes with no new features.</p>
<p>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.</p></li>
<li><p>While the 1.002xxx are being maintained as the main stable branch, I'll also be releasing 1.003_xxx versions with new features.</p></li>
<li><p>... etc...</p></li>
</ul>
<p>A wiki page can exist, with links to download tarballs of the latest releases in the 1.000xxx, 1.002xxx, etc branches.</p>
<div class="pmsig"><div class="pmsig-757127">
<small><small><tt>use Moops; class Cow :rw { has name => (default => 'Ermintrude') }; say Cow->new->name</tt></small></small>
</div></div>
1088905
1088905