--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/639528f1-a182-4818-a836-e65cfbf3d1d4%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CABexzmi8ad8r6n978Bs-O1A0_T-FX3fS%2BnJL-iGeyKokHWRJjg%40mail.gmail.com.
As a concrete example, consider a moment in time halfway between the release of Django 5.1 and 5.2. At this point in time:
- Features will be added to development master, to be released as Django 5.2.
- Critical bug fixes will be applied to the
stable/5.1.x
branch, and released as 5.1.1, 5.1.2, etc.- Security fixes and bug fixes for data loss issues will be applied to
master
and to thestable/5.1.x
,stable/5.0.x
, andstable/4.2.x
(LTS) branches. They will trigger the release of5.1.1
,5.0.5
,4.2.8
, etc.- Documentation fixes will be applied to master, and, if easily backported, to the latest stable branch,
5.1.x
.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHn91ofghfnRgfqMA7L9ntp3MgqKFr7uEw%2BRFdVKxtXMcvmU7w%40mail.gmail.com.