diff options
| author | Tim Graham <timograham@gmail.com> | 2017-09-11 09:07:14 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2017-09-11 09:07:14 -0400 |
| commit | 4844af90fb708a1fb2a25e1b8a581586678bc286 (patch) | |
| tree | a183c66be663dac6b8aa604c353188ed43b2f104 /docs/releases | |
| parent | a4092af3d33b2e7a5f05f6be3bdf8298d32d9ff8 (diff) | |
Fixed #28579 -- Doc'd upgrade effort expectations for Django 2.0.
Diffstat (limited to 'docs/releases')
| -rw-r--r-- | docs/releases/2.0.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/releases/2.0.txt b/docs/releases/2.0.txt index c744320917..fdb1d80962 100644 --- a/docs/releases/2.0.txt +++ b/docs/releases/2.0.txt @@ -11,6 +11,11 @@ want to be aware of when upgrading from Django 1.11 or earlier. We've their deprecation cycle, and we've :ref:`begun the deprecation process for some features <deprecated-features-2.0>`. +This release starts Django's use of a :ref:`loose form of semantic versioning +<internal-release-cadence>`, however, there aren't any major backwards +incompatible changes that might be expected of a 2.0 release. Upgrading should +be a similar amount of effort as past feature releases. + See the :doc:`/howto/upgrade-version` guide if you're updating an existing project. |