> > 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 the stable/5.1.x, stable/5.0.x, and 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 the latest stable branch, 5.1.x. > > I see the PR was merged at Feb 3, Django 2.2 tagged at Apr 1, so the PR is happened between 2.1 and 2.2, it should be released at 2.2 ?
On Wed, Aug 28, 2019 at 1:15 PM Jani Tiainen <[email protected]> wrote: > Oh yes there it is explained in depth > > > https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions > > ke 28. elok. 2019 klo 8.12 Jani Tiainen <[email protected]> kirjoitti: > >> It's not weird at all. Django has 8 month release cycle. Usually only >> bugs that are security issues or causes data loss are backported to older >> releases. >> >> I think this procedure is documented somewhere... >> >> ke 28. elok. 2019 klo 8.06 wd <[email protected]> kirjoitti: >> >>> It's so weird, the code is already in master 7 months, but still not >>> released yet? >>> >>> On Wed, Aug 28, 2019 at 6:09 AM John MacLaughlin < >>> [email protected]> wrote: >>> >>>> I see this ticket was addressed, fixed, and merged. However, it's not >>>> in the latest release (2.2.4) >>>> >>>> Ticket: https://code.djangoproject.com/ticket/29393 >>>> PR: https://github.com/django/django/pull/10730 >>>> >>>> How can I find out when this fix will be released? >>>> >>>> -- >>>> 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 [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/django-users/639528f1-a182-4818-a836-e65cfbf3d1d4%40googlegroups.com >>>> <https://groups.google.com/d/msgid/django-users/639528f1-a182-4818-a836-e65cfbf3d1d4%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>> -- >>> 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 [email protected]. >>> 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 >>> <https://groups.google.com/d/msgid/django-users/CABexzmi8ad8r6n978Bs-O1A0_T-FX3fS%2BnJL-iGeyKokHWRJjg%40mail.gmail.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-users/CAHn91ofghfnRgfqMA7L9ntp3MgqKFr7uEw%2BRFdVKxtXMcvmU7w%40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CAHn91ofghfnRgfqMA7L9ntp3MgqKFr7uEw%2BRFdVKxtXMcvmU7w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CABexzmj8cY3wo4mULL%3DPUhAwPq-3ACH9FrKOL5Md%3DLSp_68tQQ%40mail.gmail.com.
