On Sat, Nov 27, 2010 at 09:10:30PM -0800, Darren Duncan wrote: > With regard to the heavily updated > http://search.cpan.org/dist/Moose/lib/Moose/Manual/Support.pod as of > release 1.21 a few days ago ... > > I see that the official plan now is to release Moose on a fixed schedule > with semantically meaningful version numbers, essentially more like how > Perl itself is now released, and Parrot, Rakudo, Postgres, etc before it. > So Moose regular releases would come quarterly and minor releases > weekly, with major being defined as willing to break backwards > compatibility. > > I welcome these changes. > > Question / request: > > 1. Unless I missed it, the support document doesn't give the approximate > dates for when the quarterlies/etc are. Maybe that's because this hasn't > been decided yet, but I believe that it should be documented there once > decided, so that people can predict these things. > > 2. Have the dates been decided yet? When are the quarters?
Yes, we haven't decided on an actual release date yet; we're still working on a release plan for the new workflow. > 3. Is the next major release going to be version 2.0000 just to cleanly > setup the new semantic numbering system? The support document implies > that this would be the case. I assume you won't wait for an especially > major change to do this, even if increasing the X in X.YYZZ would > normally do that ... unless one is in the pipeline that I didn't > anticipate. Yes, the next major release will be 2.0000. We will release 1.9900 (and potentially 1.9901, etc) as trial releases prior to the actual release to allow time for testing. > 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. > -- Darren Duncan -doy