Type::Tiny Stability Policy

Type::Tiny 1.000000 is considered stable. Any changes to the API that are big enough to require changes to the test suite will be preceded by a six month notice period, with the following exceptions:

• Any changes which are necessary to maintain compatibility with new releases of Moose, Moo, and other software that Type::Tiny needs to integrate with.
• Changes to maintain compatibility with future versions of Perl itself.
• Where a change fixes a contradiction between the implementation and documentation of Type::Tiny.
• Where a feature is explicitly documented as being "experimental" or "unstable".
• Improvements to the text of error messages.

Experimental and Unstable Type::Tiny Features

The following list is currently non-exhaustive.

• Type::Tiny inlining subs (i.e. "inline_as") may return a list of strings (with "undef" being allowed as the first item on the list). This is experimental. See Type::Utils.
• Type::Tiny's "my_methods" attribute and the functionality it provides is experimental.
• The parameterizable coercion API is subject to change.
• The interaction of deep coercions and mutable coercions currently results in ill-defined behaviour. This could change at any time. (See "Deep Caveat" in Type::Tiny::Manual::Coercions.)
• Type::Registry's ability to import MooseX::Types and MouseX::Types type libraries is experimental.
• Integration with Type::Tiny::XS.
• These modules are considered part of Type::Tiny's internals, and not covered by the stability policy: Devel::TypeTiny::Perl56Compat, Devel::TypeTiny::Perl58Compat, Eval::TypeTiny, Type::Coercion::FromMoose, Type::Tiny::_HalfOp, Types::Standard::ArrayRef, Types::Standard::Dict, Types::Standard::HashRef, Types::Standard::Map, Types::Standard::ScalarRef, and Types::Standard::Tuple.
• Reply::Plugin::TypeTiny is not covered by the stability policy.

Type::Tiny Versioning Policy

As of 1.000000, this distribution follows a versioning scheme similar to Moo, which is based on a semver <http://semver.org/>-like three component version number, but with the last two components each represented by three decimal digits in the fractional part of the version number. That is, version 1.003002 of the software represents "1.3.2".

Additionally, releases where the second component is an odd number will be considered unstable/trial releases. (These will also include an underscore in the version number as per the usual CPAN convention.)