#28349: Document the recommended way to upgrade Django from LTS to LTS
--------------------------------------+------------------------------------
Reporter: eduvik | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham):
* type: Uncategorized => Cleanup/optimization
* stage: Unreviewed => Accepted
Comment:
The recommended way to upgrade from LTS to LTS is to upgrade one major
version at a time, e.g. 1.8.x -> 1.9.y -> 1.10.z -> 1.11.a. This could be
documented in `docs/howto/upgrade-version.txt`.
At the top of the release notes, it says something like "as well as some
backwards incompatible changes you’ll want to be aware of when upgrading
from Django 1.10 or older versions." I think it's fairly obvious that the
LTS release notes don't roll up all changes since the previous LTS. At
least, I haven't seen anyone else confused about that. The upgrade guide
has a link to the release notes index page, so I also don't see a need to
repeat links to the release notes for versions since the last LTS on the
release notes for an LTS.
--
Ticket URL: <https://code.djangoproject.com/ticket/28349#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.82506a683d1b00bbdd47fe504ed0c9f1%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
