From c36c7fc747dfc723bcee647103dcff0be885234f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rafael=20Mendon=C3=A7a=20Fran=C3=A7a?= Date: Fri, 30 May 2014 11:44:55 -0300 Subject: Change the version schema to reflect how deprecations are handled [ci skip] We only introduce new deprecations at Minor releases. --- guides/source/maintenance_policy.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'guides') diff --git a/guides/source/maintenance_policy.md b/guides/source/maintenance_policy.md index 05c831ac0d..6f8584b3b7 100644 --- a/guides/source/maintenance_policy.md +++ b/guides/source/maintenance_policy.md @@ -12,13 +12,13 @@ Rails follows a shifted version of [semver](http://semver.org/): **Patch `Z`** Only bug fixes, no API changes, no new features. -Except as necessary for security fixes or deprecations. +Except as necessary for security fixes. **Minor `Y`** New features, may contain API changes (Serve as major versions of Semver). -Breaking changes are paired with deprecation notices in patch level release of -the last minor version level. +Breaking changes are paired with deprecation notices in the previous minor +or major release. **Major `X`** -- cgit v1.2.3