test0908
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fixed #28579 -- Doc'd upgrade effort expectations for Django 2.0.

This commit is contained in:
Tim Graham 2017-09-11 09:07:14 -04:00 committed by GitHub
parent a4092af3d3
commit 4844af90fb
2 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/internals/release-process.txt
View File

@ -59,6 +59,8 @@ security purposes, please see :doc:`our security policies <security>`.
.. _the download page: https://www.djangoproject.com/download/ .. _the download page: https://www.djangoproject.com/download/
.. _internal-release-cadence:
Release cadence Release cadence
=============== ===============

5
docs/releases/2.0.txt
View File

@ -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 their deprecation cycle, and we've :ref:`begun the deprecation process for some
features <deprecated-features-2.0>`. 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 See the :doc:`/howto/upgrade-version` guide if you're updating an existing
project. project.