How to find out when a fix will be released

[John MacLaughlin]

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?

[wd]

It's so weird, the code is already in master 7 months, but still not released yet?

--
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.

[Jani Tiainen]

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...

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.

[Jani Tiainen]

Oh yes there it is explained in depth

https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions

[wd]

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 ?

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAHn91ofghfnRgfqMA7L9ntp3MgqKFr7uEw%2BRFdVKxtXMcvmU7w%40mail.gmail.com.

[Michal Petrucha]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Wed, Aug 28, 2019 at 01:59:01PM +0800, wd wrote:
> >
> > 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 ?

What that document doesn't explain is when the branch gets cut off for
the upcoming release, and how backporting works during the
alpha/beta/RC phase. There's a roadmap document in the wiki [1] which
indicates that your PR got merged after the alpha release, which means
in order to be included in 2.2, it would have had to be backported.
The timing is really unfortunate there, since you missed the freeze by
just a couple of weeks, but at least you can be sure that it will land
in the next major release. I also suppose asking explicitly for a
backport at the time could have helped, but it's probably too late for
that now.


[1]: https://code.djangoproject.com/wiki/Version2.2Roadmap
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEUX01Y24NsLRJUN8tcDtP8g8z+SUFAl16FaUACgkQcDtP8g8z
+SVK8xAA2QUVfi+wBAB1cjuV5cGZ7usY1kyj9aZK+iA3+zXj2yFyzpYRAPPNfr50
x3S1LrK0/GbuN5rI7IDVr/JWnduCVH8b1Kd+fFEWQyZah1XQO6HvDau5n6YFGJJC
aAVSmd4fHyAg1P4Unpyi5nRCI4hzwTQQaQEGCCkLayTS0x6uZS7ocXiBEeGoZKdt
DNg9+Fw63vJTx6CG304amN1f40lq+fcYPEQDgAMvKLNIiZ0++hILGwWZmKpY8z9G
3efyrtyrG7B8jTRyU5+adHSdMttO5eJlSj2VFlcw61oapE4sOwa7t05it0Sv/eKv
Kb1Up66lKs8FVh2G3JriQ/fxfbg4NcEJDN+mlgnKncxwcCjuyi943JFXJxtBqnM1
jnJSjceN0cYtQcsia2eO/LBeavNCwRynMtUJkA05Nu7KnJVblXqDo+GcXbHOL71m
MLm9djoR07spKDWMQLrj5Ih39uMFzQUS04Psio7J8f9aka/HYDD40nNUDymoDEWy
zBrrgd0QQmiNmhXA6CGmog2D6JNS/L8YgcFYnAk17uwk0yivVMAupojgft5IEKU8
jDDwpEluodH2VAymU+mz0YC+C+XFrpOOBo8u2a8QIbh1lsEjJRAAWG0Wk3WgXjB7
z11f8H3/bd+LRAiPOgcmzJ5WZDvL2Z0y2/YkwA9XnaijhVc7Mn0=
=zqPA
-----END PGP SIGNATURE-----