5 Moose::Manual::Support - Policies regarding support, releases, and
8 =head1 RELEASE SCHEDULE
10 Moose uses the release early, release often philosophy. Moose is not
11 released on a schedule. Releases happen as new features and bug fixes
14 There have been to date, 98 releases of Moose over just under four
15 years. This is an average of a release every two weeks.
17 =head1 DEPRECATION POLICY
19 Moose has always prioritized correctness over performance and backwards
22 Major deprecations or API changes are documented in the Changes file as
23 well as in L<Moose::Manual::Delta|Moose::Manual::Delta>
25 Moose attempts to warn for deprecated features and API changes for a
26 reasonable number of releases before breaking any tested API.
28 Moose will also warn during installation if the version being installed
29 will break a known installed dependency. Unfortunately due to the nature
30 of the Perl install process these warnings may be easy to miss.
32 =head1 BACKWARDS COMPATIBILITY
34 We try to ensure compatibility by having a extensive test suite (last
35 count just over around 5123 tests), as well as testing a number of
36 packages (currently just under 100 packages) that depend Moose before
39 The current list of downstream dependencies that are tested is in
40 C<xt/author/test-my-dependents.t>.
42 =head1 VERSION NUMBERS
44 Moose's version numbers are monotonically incrementing two decimal
45 values. The version numbers in Moose are I<not> semantic. This means
46 that version 1.00 will be the hundredth release, nothing more.
48 Moose was declared production ready at version 0.18 (via L<<
49 http://www.perlmonks.org/?node_id=608144 >>).
53 Moose has an open contribution policy. Anybody is welcome to submit a
55 L<Moose::Manual::Contributing|Moose::Manual::Contributing> for more