I'm sorry, but I still don't see how you determined that. I can follow the merge request, and the commit, but I can find anything that links to a version from either of those, though this is getting into the arena of git. I know it's in 2.0 now, but am concerned that I wasn't able to find that out just by looking at the ticket.
The Django 2.0 release notes doesn't list the bugs fixed. I think this is a critically important piece of information for many developers. Django updates can be painful, especially if you have many plugins and are a few versions behind. So when you encounter a bug that requires an upgrade, many people would want to know the lowest version they need to upgrade to to obtain a given patch (yes yes, everyone should update to latest, but there are always reasons that can't be done, or trade-offs, which then become business decisions etc...) On Wed, Dec 20, 2017 at 8:11 PM, Jani Tiainen <rede...@gmail.com> wrote: > Hi. > > Usually when ticket is closed there is a pointer to changeset which fixed > the issue. When you look the changeset it should also contain a list of > tags that are in effect in that changeset. > > By looking that ticket it was fixed in master branch and then backported > to 2.0.x branch. > > In this case it's not very obvious that issue is fixed in 2.0+ > > > 20.12.2017 8.33 ip. "Andrew Buchan" <andyha...@gmail.com> kirjoitti: > > I'm being affected by this bug: https://code.djangoproject.com > /ticket/28562 which was fixed 4 months ago. > > Somewhere on the ticket page it says: > > Version: 1.11 → master > Which is the only reference to version I found anywhere on the page, so I > assumed this meant the fix was in 1.11 > > I've just spent 2 days going through a ridiculously difficult upgrade, > only to find that this fix is not in 1.11! > > So how do I know which version a given bug has been fixed in, short of > examining the source code myself? > > -- > 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+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ms > gid/django-users/7838c495-3174-4393-a0e1-ca481e0596be%40googlegroups.com > <https://groups.google.com/d/msgid/django-users/7838c495-3174-4393-a0e1-ca481e0596be%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Django users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/django-users/XamGT196Svc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > django-users+unsubscr...@googlegroups.com. > To post to this group, send email to django-users@googlegroups.com. > Visit this group at https://groups.google.com/group/django-users. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/django-users/CAHn91od_ojscGPU4yao_M3i5BtJ58ff1Xr39WWME7zH6nedvmg > %40mail.gmail.com > <https://groups.google.com/d/msgid/django-users/CAHn91od_ojscGPU4yao_M3i5BtJ58ff1Xr39WWME7zH6nedvmg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAEtX%2BfD1LPjF6cHSPnd9ZhSDhowZDm1bMJ18qhHtCnsW4xF7Pg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
