109012 - Hackers' Guide - The three questions.

Status: RESOLVED FIXED

(Bugzilla :: bugzilla.org, defect, P3)

Description

[Matthew Tuck [:CodeMachine]]

Whenever you're fixing a bug, you should ask yourself three questions:

1. Where else in the codebase might this bug occur.  Make sure these are fixed
as well or reported.
2. How could you, or the Bugzilla team in general, prevent this problem in
future?  Consider reusable subs that could be introduced, or tests that could be
added to the testing suite.
3. Could this have regressed anything?

Comment 1

[Dave Miller [:justdave]]

We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.

Comment 2

[Dave Miller [:justdave]]

The docs should always be up-to-date when we release.  Forgot to exclude
Documentation when I mass-retargetted.

Comment 3

[Matthew Tuck [:CodeMachine]]

Moving process information bug to the web site component and taking them.

Comment 4

[Matthew Tuck [:CodeMachine]]

This is in baby, let's have a party!