#28349: Release notes should detail which version they're 'coming from' and LTS
release notes should include/link all changes since previous LTS
-----------------------------------------+------------------------
Reporter: eduvik | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 1
UI/UX: 0 |
-----------------------------------------+------------------------
If I want to upgrade from the previous LTS (1.8) to the current (1.11)
(presumably a common upgrade path) and go to the release
notes/incompatible changes for 1.11
(https://docs.djangoproject.com/en/1.11/releases/1.11/#backwards-
incompatible-changes-in-1-11) then it doesn't specify which version the
changes are incompatible with. Firstly, (for LTS releases at least) it
would be good to say something like 'changes since version 1.10'.
Secondly, for LTS releases, it would be ideal to 'roll up' all backwards
incompatible changes (or even all changes) since the last LTS, or, failing
that, include links to all of the release notes since the previous LTS.
--
Ticket URL: <https://code.djangoproject.com/ticket/28349>
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/049.64e75cf665fc286f0b367a9d69c14e19%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
