X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FMoose%2FManual%2FContributing.pod;h=76858f88f9f0a4efc552239c4f3926edc05c4b35;hb=86b96832857ac808a75cecdb2880513753f483e8;hp=8bf7ffef9b1be3d2eb36593f386fbf7c6ffd7c00;hpb=52da380a9111c74467177526f792a898b412591a;p=gitmo%2FMoose.git diff --git a/lib/Moose/Manual/Contributing.pod b/lib/Moose/Manual/Contributing.pod index 8bf7ffe..76858f8 100644 --- a/lib/Moose/Manual/Contributing.pod +++ b/lib/Moose/Manual/Contributing.pod @@ -65,13 +65,13 @@ an entry in the Changes file. Make sure to give yourself credit! =head1 BACKWARDS COMPATIBILITY Change is inevitable and Moose is not immune to this. We do our best -to maintain backwards compatability, but we do not want the codebase +to maintain backwards compatibility, but we do not want the code base to become overburdened by this. This is not to say that we will be frivolous with our changes, quite the opposite, just that we are not afraid of change and will do our best to keep it as painless as possible for the end user. -The rule is that if you do something that is not backwards compatabile +The rule is that if you do something that is not backwards compatible you B do I one deprecation cycle (more if it is larger change). For really larger or radical changes dev releases may be needed as well (the core developers will decide on this on a @@ -81,7 +81,7 @@ The preference with regard to deprecation is to warn loudly and often so that users will have time to fix their usages. All backwards incompatible changes B be documented in -L. Mke sure to document any useful tips or +L. Make sure to document any useful tips or workarounds for the change in that document. =head1 AUTHOR