From 4844af90fb708a1fb2a25e1b8a581586678bc286 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 11 Sep 2017 09:07:14 -0400 Subject: [PATCH] Fixed #28579 -- Doc'd upgrade effort expectations for Django 2.0. --- docs/internals/release-process.txt | 2 ++ docs/releases/2.0.txt | 5 +++++ 2 files changed, 7 insertions(+) diff --git a/docs/internals/release-process.txt b/docs/internals/release-process.txt index a03d85036a..dc6d9a0696 100644 --- a/docs/internals/release-process.txt +++ b/docs/internals/release-process.txt @@ -59,6 +59,8 @@ security purposes, please see :doc:`our security policies `. .. _the download page: https://www.djangoproject.com/download/ +.. _internal-release-cadence: + Release cadence =============== 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 `. +This release starts Django's use of a :ref:`loose form of semantic versioning +`, 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.