Thank you Tobias. Good explanation. An additional point I picked up from Tim is that if you have a Reproduced at... but the bug is fixed on master then you have a starting point to git bisect where the issue was fixed.
On Sat, 11 May 2019 at 15:28, Tobias Kunze <r...@rixx.de> wrote: > Hi Ruchit, > > On 19-05-10 23:19:16, Ruchit Vithani wrote: > >I have following queries regarding tickets on Trac. In many of the > tickets, > >some people comment `Regression in` and `Reproduced at`, and both of them > >link to some commit on GitHub. I could not understand what these links > >specify. > > The "regression in" comments point to commits that have either > introduced or re-introduced the issue in the ticket. Regressions are > explained in the contributing documentation, including a guide on how to > figure out which commit caused the regression: > < > https://docs.djangoproject.com/en/2.2/internals/contributing/triaging-tickets/#bisecting-a-regression > > > > This is helpful because it gives you a start when trying to fix the > issue. You can look at the causing commit, and figure out if this > behaviour was intentional, if it was discussed in the ticket referenced > in the commit, if it was accidental, etc. It also helps you to develop a > fix that doesn't break anything else unintentionally. So even if you > don't have the time or experience to find a fix, finding and noting > which commit caused a regression can be very helpful. > > The 'reproduced at' comments are indeed not mentioned in the triage > documentation – maybe you could add them? Sometimes people add comments > like that when they accept a ticket, for better documentation of why > they decided to accept a ticket. There is a note about this workflow > here: > https://docs.djangoproject.com/en/2.2/internals/contributing/new-contributors/ > > They can also be useful with old tickets: With more than a thousand > open tickets, and most of them older than the last one or two releases, > it's not always obvious that an issue still persists. (For instance, I > recently came across a ticket that called for the introduction of > template-based form rendering, which has been part of Django for some > time now.) Adding a comment that the issue still persists currently (and > linking to the tested commit for reference) can be helpful to show that > an 8 year old bug is still relevant. > > I hope this helps, > Tobias > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/20190511132755.gmpmcetv33npqlji%40cordelia.localdomain > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAJwKpyRmus1j7xwz2NEjbzUYN1ncft0vu0uCqh6x8_xsebnCxA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
