-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: django
-
None
Context
There is currently no mechanism for tracking which fixes on main need to be backported to an active LTS branch (e.g. 5.2.x).
The supported versions policy in docs/internals/release-process.rst states that only security fixes and data-loss bugs are applied to the previous feature release and active LTS branches.
Definition of done
Add a "Backporting" section to docs/internals/release-process.rst covering: what qualifies for backport under the supported versions policy.
Pitfalls
None
- is duplicated by
-
INTPYTHON-1077 [Django] ADD INSTRUCTIONS ON Tracking upstream stable/A.B.x backports for django-mongodb-backend A.B.x+1
-
- Closed
-