Jesse, thank you for your quick reply.
As it is, I had also discovered
http://blog.moose.perl.org/2010/11/the-future-of-moose.html after sending my
post, although it didn't answer everything.
Jesse Luehrs wrote:
On Sat, Nov 27, 2010 at 09:10:30PM -0800, Darren Duncan wrote:
<snip>
4. Is Class::MOP going to gain a similar support policy to Moose's new
one, considering how closely they are associated?
Class::MOP will likely be folded into the Moose dist directly sometime
quite soon (either as part of 2.0000, or the next major release after
that), with a end goal of removing it entirely, and moving its
functionality entirely into Moose. If we decide to leave Class::MOP
separate for Moose-2.0000, it will also be released as Class-MOP-2.0000.
If you know for certain that Class::MOP will soon be rolled in anyway, then I
strongly prefer the merger happen before/with Moose 2.0 rather than 3 months later.
That's just one of those kinds of things that would really make the 2.0 moniker
/ X increment truly meaningful content-wise and not just be to start off the
renumbering. Then we also avoid seeing a Class::MOP 2.0 major release that then
promptly disappears afterwards.
According to the above url, a lot of redundant code between the Class::MOP and
Moose was refactor-eliminated anyway, and that looks like a step towards merger
anyway.
I would only release Moose-2.0 without an included Class::MOP if there was any
second thoughts about the latter not staying separate longer term.
-- Darren Duncan
