Closed
Bug 76639
Opened 24 years ago
Closed 15 years ago
Maintainer should be automatically set.
Categories
(Bugzilla :: Installation & Upgrading, enhancement, P3)
Tracking
()
RESOLVED
FIXED
Bugzilla 3.6
People
(Reporter: CodeMachine, Assigned: mkanat)
References
Details
(Whiteboard: [fixed by blocker])
The maintainer field on editparams.cgi should be set by checksetup.pl from the email account of the first account created by it.
Comment 1•24 years ago
|
||
This will be a nice trick, since checksetup.pl has no access to the Params unless we duplicate a whole mess of code. I agree it's a good idea though. Hmm, on second thought, assuming that data/params doesn't exist yet, a very simplified data/params could probably be written out that contained only the maintainer param. The rest of the params would be picked up from defparams.pl the next time it tries to reference a param that hasn't been defined yet.
Reporter | ||
Updated•24 years ago
|
Target Milestone: --- → Bugzilla 2.16
Reporter | ||
Updated•23 years ago
|
Priority: -- → P3
Reporter | ||
Comment 2•23 years ago
|
||
Moving to new Bugzilla product ...
Assignee: tara → zach
Component: Bugzilla → Installation
Product: Webtools → Bugzilla
Version: Bugzilla 2.11 → 2.13
Comment 3•23 years ago
|
||
This should be very easy, just add $::param{'maintainer'}="foobar"; to data/params unless (-e data/params);
Updated•23 years ago
|
Status: NEW → ASSIGNED
Comment 4•23 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 5•21 years ago
|
||
These unloved bugs have been sitting untouched since June 2002 or longer. If nobody does anything else to them, they certainly won't make 2.18 Retargetting to 2.20. If you really plan to push them right now, you might pull them back in.
Target Milestone: Bugzilla 2.18 → Bugzilla 2.20
Assignee | ||
Comment 6•20 years ago
|
||
This bug has not been touched by its owner in over six months, even though it is targeted to 2.20, for which the freeze is 10 days away. Unsetting the target milestone, on the assumption that nobody is actually working on it or has any plans to soon. If you are the owner, and you plan to work on the bug, please give it a real target milestone. If you are the owner, and you do *not* plan to work on it, please reassign it to nobody@bugzilla.org or a .bugs component owner. If you are *anybody*, and you get this comment, and *you* plan to work on the bug, please reassign it to yourself if you have the ability.
Target Milestone: Bugzilla 2.20 → ---
Updated•18 years ago
|
Severity: minor → trivial
Updated•18 years ago
|
QA Contact: mattyt-bugzilla → default-qa
Assignee | ||
Comment 7•18 years ago
|
||
This actually could be done nowadays, with the checksetup re-write.
Assignee: zach → mkanat
Status: ASSIGNED → NEW
Assignee | ||
Updated•18 years ago
|
Severity: trivial → enhancement
Comment 8•15 years ago
|
||
Will be fixed as part of bug 519858.
Assignee | ||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Whiteboard: [blocker will fix] → [fixed by blocker]
You need to log in
before you can comment on or make changes to this bug.
Description
•