diff options
| author | Tom Christie | 2014-09-19 14:31:49 +0100 |
|---|---|---|
| committer | Tom Christie | 2014-09-19 14:31:49 +0100 |
| commit | ce165805481988e95887bf62c45cd616af5bba0f (patch) | |
| tree | 8a8852980756b96d99eb637cdf0358c9bb16bbdf | |
| parent | e6d4445bbbb30531ea98164379cfb707bcc8415f (diff) | |
| download | django-rest-framework-ce165805481988e95887bf62c45cd616af5bba0f.tar.bz2 | |
Tweak
| -rw-r--r-- | topics/release-notes.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/topics/release-notes.html b/topics/release-notes.html index 256d0496..4f8ebe66 100644 --- a/topics/release-notes.html +++ b/topics/release-notes.html @@ -217,7 +217,7 @@ a.fusion-poweredby { <h2 id="versioning">Versioning</h2> <p>Minor version numbers (0.0.x) are used for changes that are API compatible. You should be able to upgrade between minor point releases without any other code changes.</p> <p>Medium version numbers (0.x.0) may include API changes, in line with the <a href="#deprecation-policy">deprecation policy</a>. You should read the release notes carefully before upgrading between medium point releases.</p> -<p>Major version numbers (x.0.0) are reserved for substantial project milestones. No major point releases are currently planned.</p> +<p>Major version numbers (x.0.0) are reserved for substantial project milestones.</p> <h2 id="deprecation-policy">Deprecation policy</h2> <p>REST framework releases follow a formal deprecation policy, which is in line with <a href="https://docs.djangoproject.com/en/dev/internals/release-process/#internal-release-deprecation-policy">Django's deprecation policy</a>.</p> <p>The timeline for deprecation of a feature present in version 1.0 would work as follows:</p> |