Django's oldest ticket is EIGHT YEARS old. Wowzers. It is not, however, a bug problem- it is a new feature- involving the admin interfaces. This new feature would make it possible to have multiple fields worth of data entered in a single field. This is the example they provide:
"For example, a field for a sports stat could be entered into a single field as "XX-YY-ZZ", whereas the three values are actually three separate fields in the DB."
The current triage stage is "Someday/Maybe" so I do not think that this new feature is of top priority- obviously- since it's been 8 years. But I do see some involvement in the comments from core developers...but that was...ummm...TWO years ago.
Task: Figure out how to create a new account on the bug tracker of your chosen project. You'll need that account very soon.
It was super simple to join Django's bug tracker, but they call it a "ticket system". I am now registered.
Task: Go through your project's bug tracker and find a bug that you think you might be able to reproduce -- and then try to reproduce it in the latest build. Take careful notes. Report your experiences as a comment to the bug. If you can reproduce the bug, great! Give as much information as you can. If you can't reproduce the bug, great! Give as much information as you can, and ask the original reporter if there are other steps you might be able to take to reproduce the bug.
This ticket reported a bug that produced an error when a field from a subclass was moved to its base class. One of the core developers responded to this ticket giving instructions on how to reproduce the error step-by-step. I followed it exactly, but could not reproduce the error.
What I did:
- I had the subclass and base class in their original positions --> $ python manage.py makemigrations
- Switched their positions, saved the file --> $ python manage.py makemigrations
- After running that command on both those versions, $ python manage.py migrate, was suppose to cause the error, but it did not.
Task: Find five bug reports in the new state, and attempt to triage them according to the rules above. Your goal is to do as much as you possibly can, in a short period of time, to make those bug reports as useful as possible to the developer to whom they are assigned. (Note: be sure to follow any triage rules that your project may have defined. If there are no set triage rules, be sure to announce your intentions on the project's mailing list, so that developers can provide you some guidelines if they choose.)
There was one new ticket that was only 3 hours old so I was able to add this "helpful" comment:
"Hi, thanks for reporting. Do you mind giving more information on how to reproduce this exception so a newbie could partake? Thanks!"
This ticket did not contain any software versions nor was it very descriptive. But that was about the only ticket I saw that I could help triage. Django's triaging system seems to be really organized and people are quick to comment and move the ticket along the triaging line.
No comments:
Post a Comment