<div dir="ltr"><div class="gmail_extra">On Tue, Oct 4, 2016 at 4:35 PM, Christian Walde <span dir="ltr"><<a href="mailto:walde.christian@gmail.com" target="_blank">walde.christian@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">[Peter] preparing [his] feature-frozen-bugfix-only release in a different<br>
namespace; mst's plan being used in the DBIx::Class namespace.<br>
</blockquote></div><br></div><div class="gmail_extra">Speaking for myself (not for PAUSE admins), I think it's worth considering the opposite as well:<br><br></div><div class="gmail_extra">* DBIx::Class (DBIC) – Peter's work provides a capstone, with only bug fixes thereafter<br></div><div class="gmail_extra">* DBIx::Class2 (DBIC2) – new feature development, with lower stability expectations<br><br></div><div class="gmail_extra">Some of the benefits I could see from this:<br><br></div><div class="gmail_extra">(1) It helps DBIC users avoid getting upgraded past a stability point without having to learn to pin module versions or change application code to use a different package name. People have to positively opt-in for some risk in exchange for new features by asking for DBIC2 explicitly.<br><br></div><div class="gmail_extra">(2) The relation between the two is more immediately obvious than between, say, DBIx::Class::Stable and DBIx::Class. It also seems more like one project than two, particularly if both are under the same governance, use the same mailing list, etc.<br><br></div><div class="gmail_extra">(3) It sets a possible path forward of DBIC2 evolving new features for a while and then eventually moving into a bug-fix-only state while the next generation of new features go into a future DBIC3.<br><br></div><div class="gmail_extra">There is some precedent for "Foo" evolution going to "Foo2" such as Dancer/Dancer2, Test/Test2, and probably others. Those have bigger disruptions from old to new than I imagine DBIC2 having (initial release of DBI2 probably being a carbon copy of the final version of DBIC), but at least its a naming pattern that people will recognize.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Sincerely,<br></div><div class="gmail_extra">David<br></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>David Golden <<a href="mailto:xdg@xdg.me" target="_blank">xdg@xdg.me</a>> Twitter/IRC/GitHub: @xdg</div></div></div></div></div>
</div></div>