Closed
Bug 98049
Opened 24 years ago
Closed 24 years ago
Hacker's guide should mention sanity check.
Categories
(Bugzilla :: Documentation, defect, P2)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.16
People
(Reporter: CodeMachine, Assigned: barnboy)
Details
Sanity check tends to lag behind the schema, so we should aim to get people to
update it when they make schema changes.
Basically, we should add something to the hackers' guide saying that when you
make schema changes you should think about modifying sanity check to support the
new schema. All referential columns should be checked.
| Reporter | ||
Updated•24 years ago
|
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.16
Comment 1•24 years ago
|
||
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.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18
Comment 2•24 years ago
|
||
The docs should always be up-to-date when we release. Forgot to exclude
Documentation when I mass-retargetted.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.16
| Assignee | ||
Comment 3•24 years ago
|
||
Added blurb about this to the Guide in bzhacking.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•