This Bugs Me

6.4 Find the oldest bug that’s still open in your chosen project. Write a blog entry describing the problem, with a theory about why the bug hasn’t been resolved yet. (Bonus points if you can actually resolve the bug.)

• The oldest open issue for OpenPetra is “Print Posting Register after posting a batch only works with FastReports.” This issue was posted December 4th, 2014 and has been marked as a low priority. This is more of a feature request than a bug as there is already a way to print the statement under fast reports.

6.5 Figure out how to create a new account on the bug tracker of your chosen project. You’ll need that account very soon.

• OpenPetra utilizes GitHub’s issues tracker, and I have already forked the project to my repository so there is no need to set-up an issue tracker account.

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

• The first bug we chose to tackle as a team was the easiest to reproduce. We have actually fixed this bug and submitted a pull request from our repo. Now the bug in question is “Fix missing translation in LedgerSetup.entry_first_current_period.” This bug is caused due to there being a missnamed dictionary term in the project which causes the variable name to show up instead of the desired result. Recreating the bug is as simple as opening a demo of OpenPetra and navigating to the correct tab to view where the variable name is being presented.

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

• The creator of OpenPetra submits all issues himself into the issue tracker, and keeps it organized the way he sees fit.