update the support policy with changes to time-box the release schedule

diff --git a/lib/Moose/Manual/Support.pod b/lib/Moose/Manual/Support.pod
index 2b7b7db..db67625 100644 (file)
--- a/lib/Moose/Manual/Support.pod
+++ b/lib/Moose/Manual/Support.pod
@@ -7,12 +7,20 @@ compatibility.
 
 =head1 RELEASE SCHEDULE
 
-Moose uses the release early, release often philosophy. Moose is not
-released on a schedule. Releases happen as new features and bug fixes
-are required.
+Moose uses the release early, release often philosophy. 
 
-Moose has historically been released fairly often, and most releases include
-just a few features or bug fixes.
+Moose is on a system of monthly 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.
+
+Major releases are potentially backwards incompatibiliy. Moose prioritizes correcness over backwards
+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.
 
 =head1 DEPRECATION POLICY