Fixed docs: release-process, Supported Versions section, concrete example
Security & data loss fixes are applied to the two last feature releases, not just one. Thanks Loic Bistuer for review
This commit is contained in:
parent
b84f5ab4ec
commit
3dd4e9203a
|
@ -163,8 +163,9 @@ Django 5.1 and 5.2. At this point in time:
|
||||||
released as 5.1.1, 5.1.2, etc.
|
released as 5.1.1, 5.1.2, etc.
|
||||||
|
|
||||||
* Security fixes and bug fixes for data loss issues will be applied to
|
* Security fixes and bug fixes for data loss issues will be applied to
|
||||||
``master`` and to the ``stable/5.1.x``, and ``stable/4.2.x`` (LTS) branches.
|
``master`` and to the ``stable/5.1.x``, ``stable/5.0.x`` and
|
||||||
They will trigger the release of ``5.1.1``, ``4.2.1``, etc.
|
``stable/4.2.x`` (LTS) branches.
|
||||||
|
They will trigger the release of ``5.1.1``, ``5.0.5``, ``4.2.8``, etc.
|
||||||
|
|
||||||
* Documentation fixes will be applied to master, and, if easily backported, to
|
* Documentation fixes will be applied to master, and, if easily backported, to
|
||||||
the latest stable branch, ``5.1.x``.
|
the latest stable branch, ``5.1.x``.
|
||||||
|
|
Loading…
Reference in New Issue