Moose::Manual::Support - Policies regarding support, releases, and
compatibility.
+=head1 SUPPORT POLICY
+
+There are two principles to Moose's Policy of Supported Behavior
+
+1. Moose favors correctness over everything.
+2. Moose supports documented and tested behavior, not accidental behavior or side effects.
+
+If a behavior has never been documented or tested, the behavior is I<officially> undefined. Relying
+upon undocumented and untested behavior is done at your own risk.
+
+If a behavior is documented or tested but found to be incorrect later, the behavior will go through a
+deprecation period in which it warns before being removed.
+
=head1 RELEASE SCHEDULE
Moose uses the release early, release often philosophy.
-Moose is on a system of monthly minor Releases, and quarterly major releases. A minor release is
+Moose is on a system of weekly minor releases, and quarterly major releases. A minor release is
deifined as one that makes every attempt to not break backwards compatibility. Currently this means
that the dependency conflict lists, and test suite did not change substantially, or that any changes
were additive.
compatibility or performance, see the Deprecation Policy below for how backwards incompatible changes
are announced.
-Between the last minor release and the next major release, a series of Development Releases will be
-made so that users can test the upcoming major release before it is distributed to CPAN. It is in the
-best interests of everyone involved if these releases are tested as widely as possible.
+Before a major release, a series of Development Releases will be made so that users can test the
+upcoming major release before it is distributed to CPAN. It is in the best interests of everyone
+involved if these releases are tested as widely as possible.
=head1 DEPRECATION POLICY
projects / gitmo/Moose.git / blobdiff