{ "mode": "perldoc", "parameter": "Moose::Manual::Support", "section": "", "url": "https://www.chedong.com/phpMan.php/perldoc/Moose%3A%3AManual%3A%3ASupport/json", "generated": "2026-06-12T18:46:16Z", "sections": { "NAME": { "content": "Moose::Manual::Support - Policies regarding support, releases, and compatibility.\n", "subsections": [] }, "VERSION": { "content": "version 2.2200\n", "subsections": [] }, "SUPPORT POLICY": { "content": "There are two principles to Moose's policy of supported behavior.\n\n1. Moose favors correctness over everything.\n\n2. Moose supports documented and tested behavior, not accidental behavior or side effects.\n\nIf a behavior has never been documented or tested, the behavior is *officially* undefined.\nRelying upon undocumented and untested behavior is done at your own risk.\n\nIf a behavior is documented or tested but found to be incorrect later, the behavior will go\nthrough a deprecation period. During the deprecation period, use of that feature will cause a\nwarning. Eventually, the deprecated feature will be removed.\n\nIn some cases, it is not possible to deprecate a behavior. In this case, the behavior will\nsimply be changed in a major release.\n", "subsections": [] }, "RELEASE SCHEDULE": { "content": "Moose is on a system of quarterly major releases, with minor releases as needed between major\nreleases. A minor release is defined as one that makes every attempt to preserve backwards\ncompatibility. Currently this means that we did not introduce any new dependency conflicts, and\nthat we did not make any changes to documented or tested behavior (this typically means that\nminor releases will not change any existing tests in the test suite, although they can add new\nones). A minor release can include new features and bug fixes.\n\nMajor releases may be backwards incompatible. Moose prioritizes correctness over backwards\ncompatibility or performance; see the DEPRECATION POLICY to understand how backwards\nincompatible changes are announced.\n\nMajor releases are scheduled to happen during fixed release windows. If the window is missed,\nthen there will not be a major release until the next release window. The release windows are\none month long, and occur during the months of January, April, July, and October.\n\nBefore a major release, a series of development releases will be made so that users can test the\nupcoming major release before it is distributed to CPAN. It is in the best interests of everyone\ninvolved if these releases are tested as widely as possible.\n", "subsections": [] }, "DEPRECATION POLICY": { "content": "Moose has always prioritized correctness over performance and backwards compatibility.\n\nMajor deprecations or API changes are documented in the Changes file as well as in\nMoose::Manual::Delta. The Moose developers will also make an effort to warn users of upcoming\ndeprecations and breakage through the Moose blog (http://blog.moose.perl.org).\n\nDeprecated APIs will be preserved for at least one year *after the major release which\ndeprecates that API*. Deprecated APIs will only be removed in a major release.\n\nMoose will also warn during installation if the version of Moose being installed will break an\ninstalled dependency. Unfortunately, due to the nature of the Perl install process these\nwarnings may be easy to miss.\n", "subsections": [] }, "BACKWARDS COMPATIBILITY": { "content": "We try to ensure compatibility by having a extensive test suite (last count over 18000 tests),\nas well as testing a number of packages (currently just under 100 packages) that depend on Moose\nbefore any release.\n\nThe current list of downstream dependencies that are tested is in\n\"xt/author/test-my-dependents.t\".\n", "subsections": [] }, "VERSION NUMBERS": { "content": "Moose version numbers consist of three parts, in the form X.YYZZ. The X is the \"special magic\nnumber\" that only gets changed for really big changes. Think of this as being like the \"5\" in\nPerl 5.12.1.\n\nThe YY portion is the major version number. Moose uses even numbers for stable releases, and odd\nnumbers for trial releases. The ZZ is the minor version, and it simply increases monotonically.\nIt starts at \"00\" each time a new major version is released.\n\nSemantically, this means that any two releases which share a major version should be\nAPI-compatible with each other. In other words, 2.0200, 2.0201, and 2.0274 are all\nAPI-compatible.\n\nPrior to version 2.0, Moose version numbers were monotonically incrementing two decimal values\n(0.01, 0.02, ... 1.11, 1.12, etc.).\n\nMoose was declared production ready at version 0.18 (via\n).\n", "subsections": [] }, "PERL VERSION COMPATIBILITY": { "content": "As of version 2.16, Moose will officially support being run on perl 5.10.1+. Our current policy\nis to support the earliest version of Perl shipped in the latest stable release of any major\noperating system (this tends to mean CentOS). We will provide at least six months notice (two\nmajor releases) when we decide to increase the officially supported Perl version.\n\n\"Officially supported\" does not mean that these are the only versions of Perl that Moose will\nwork with. Our declared perl dependency will remain at 5.8.3 as long as our test suite continues\nto pass on 5.8.3. What this does mean is that the core Moose dev team will not be spending any\ntime fixing bugs on versions that aren't officially supported, and new contributions will not be\nrejected due to being incompatible with older versions of perl except in the most trivial of\ncases. We will, however, still welcome patches to make Moose compatible with earlier versions,\nif other people are still interested in maintaining compatibility. As such, the current minimum\nrequired version of 5.8.3 will remain for as long as downstream users are happy to assist with\nmaintenance.\n\nNote that although performance regressions are acceptable in order to maintain backwards\ncompatibility (as long as they only affect the older versions), functionality changes and buggy\nbehavior will not be. If it becomes impossible to provide identical functionality between modern\nPerl versions and unsupported Perl versions, we will increase our declared perl dependency\ninstead.\n", "subsections": [] }, "CONTRIBUTING": { "content": "Moose has an open contribution policy. Anybody is welcome to submit a patch. Please see\nMoose::Manual::Contributing for more details.\n", "subsections": [] }, "AUTHORS": { "content": "* Stevan Little \n\n* Dave Rolsky \n\n* Jesse Luehrs \n\n* Shawn M Moore \n\n* יובל קוג'מן (Yuval Kogman) \n\n* Karen Etheridge \n\n* Florian Ragwitz \n\n* Hans Dieter Pearcey \n\n* Chris Prather \n\n* Matt S Trout \n", "subsections": [] }, "COPYRIGHT AND LICENSE": { "content": "This software is copyright (c) 2006 by Infinity Interactive, Inc.\n\nThis is free software; you can redistribute it and/or modify it under the same terms as the Perl\n5 programming language system itself.\n", "subsections": [] } }, "summary": "Moose::Manual::Support - Policies regarding support, releases, and compatibility.", "flags": [], "examples": [], "see_also": [] }