I'm surprised this bug isn't already filed, but apparently it isn't. For Bugzilla 3.2, one of our primary goals is to move the bug-update code from process_bug into Bug.pm. We will do this incrementally, in separate bugs, the same way we did post_bug. We should tackle the easiest columns first, like bug_file_loc and status_whiteboard and things like that. For a while, I think $bug->update wil have to co-exist with the UPDATE statement that lives in process_bug--that is, for a while during the development cycle of 3.2, there will be hacks in process_bug to make Bugzilla::Bug and old-style direct-SQL work together.
This will block 3.2rc1, but not 3.1.2.
Flags: blocking3.1.2? → blocking3.1.2-
As far as I'm concerned, everything that had to be implemented for 3.1.3 in this bug is done, and the rest only must be completed before 3.2. So, I'm removing the blocking3.1.3 flag and setting blocking3.2.
Status: NEW → ASSIGNED
Flags: blocking3.1.3+ → blocking3.2+
Okay, this is done, as far as we're going to get for 3.2. Everything else has been moved to blocking bug 122922. Thanks to everybody who helped with this (mostly me and LpSolit, I suppose). :-) This was probably the largest refactoring in Bugzilla's history.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.