Bug 367914 (bz-process_bug)

Move process_bug code into Bug.pm (make Bug.pm able to update bugs)

RESOLVED FIXED in Bugzilla 3.2

Status

()

Bugzilla
Creating/Changing Bugs
--
enhancement
RESOLVED FIXED
12 years ago
10 years ago

People

(Reporter: Max Kanat-Alexander, Assigned: Max Kanat-Alexander)

Tracking

(Blocks: 1 bug, {meta})

unspecified
Bugzilla 3.2
Dependency tree / graph
Bug Flags:
blocking3.2 +
blocking3.1.2 -

Details

(Whiteboard: [roadmap: 3.2])

(Assignee)

Description

12 years ago
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.
(Assignee)

Updated

12 years ago
Blocks: 366296

Updated

12 years ago
Keywords: meta
Whiteboard: [roadmap: 3.2]
(Assignee)

Updated

12 years ago
Depends on: 371070
(Assignee)

Updated

12 years ago
Depends on: 283926
(Assignee)

Updated

12 years ago
Depends on: 372700
(Assignee)

Updated

12 years ago
Blocks: 119569
(Assignee)

Updated

11 years ago
Depends on: 373660
(Assignee)

Updated

11 years ago
Depends on: 373689
(Assignee)

Updated

11 years ago
Depends on: 384651
(Assignee)

Updated

11 years ago
Depends on: 384664
(Assignee)

Updated

11 years ago
Depends on: 385379
(Assignee)

Updated

11 years ago
Depends on: 385849
(Assignee)

Updated

11 years ago
Blocks: 387265
(Assignee)

Updated

11 years ago
Depends on: 388022
(Assignee)

Updated

11 years ago
Depends on: 388036
(Assignee)

Updated

11 years ago
Depends on: 388045
(Assignee)

Updated

11 years ago
Depends on: 388147
(Assignee)

Updated

11 years ago
Depends on: 388149

Updated

11 years ago
Flags: blocking3.1.2?
(Assignee)

Comment 1

11 years ago
This will block 3.2rc1, but not 3.1.2.
Flags: blocking3.1.2? → blocking3.1.2-
(Assignee)

Updated

11 years ago
Depends on: 396971
(Assignee)

Updated

11 years ago
No longer depends on: 396971

Updated

11 years ago
Blocks: 143313
(Assignee)

Updated

11 years ago
Blocks: 399482
(Assignee)

Updated

11 years ago
Assignee: create-and-change → mkanat
(Assignee)

Updated

11 years ago
Depends on: 401953
(Assignee)

Updated

11 years ago
Depends on: 401957
(Assignee)

Updated

11 years ago
Depends on: 401965
(Assignee)

Updated

11 years ago
Flags: blocking3.2+
(Assignee)

Updated

11 years ago
Depends on: 402791

Updated

11 years ago
Blocks: 121069
(Assignee)

Updated

11 years ago
Flags: blocking3.2+ → blocking3.1.3+
(Assignee)

Updated

11 years ago
Depends on: 412836
(Assignee)

Updated

11 years ago
Depends on: 413183
(Assignee)

Updated

11 years ago
Depends on: 413184

Updated

11 years ago
Depends on: 413215
(Assignee)

Comment 2

11 years ago
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+

Updated

11 years ago
Depends on: 415541
(Assignee)

Updated

11 years ago
Blocks: 415813
(Assignee)

Updated

11 years ago
No longer depends on: 415541

Updated

11 years ago
Blocks: 354320
(Assignee)

Updated

10 years ago
No longer depends on: 413183
(Assignee)

Updated

10 years ago
No longer depends on: 413215
(Assignee)

Comment 3

10 years ago
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.