Closed
Bug 708505
Opened 14 years ago
Closed 14 years ago
remove "needs-reconfig" flag for all RelEng, IT and Testing components
Categories
(bugzilla.mozilla.org :: General, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: dkl)
Details
RelEng has changed how we do reconfigs, and how we accept code changes from other groups that need to be rolled out to production.
We've used this new process for a few months now, and feel confident we no longer need the "needs-reconfig" file for tracking pending reconfigs. Removing this obsolete flag would reduce confusion.
| Assignee | ||
Updated•14 years ago
|
Assignee: nobody → dkl
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•14 years ago
|
||
Here is the current list of product/component combinations that the needs-reconfig
flag is visible for. Let me know which ones from the list you no longer need the
flag.
Product:Component
-------------------------------
Testing:General
Testing:Infrastructure
Testing:Mozmill
Testing:New Frameworks
Testing:Talos
mozilla.org:MozillaBuild
mozilla.org:Release Engineering
mozilla.org:Release Engineering: Custom Builds
One thing to note is that the flags will be removed from the current bugs
under the product/component and will not be recoverable. Let me know if
this is ok as well.
dkl
Comment 2•14 years ago
|
||
(In reply to David Lawrence [:dkl] from comment #1)
> One thing to note is that the flags will be removed from the current bugs
> under the product/component and will not be recoverable. Let me know if
> this is ok as well.
Why not just mark it inactive? Destroying history is never a good thing, generally.
| Assignee | ||
Comment 3•14 years ago
|
||
Because it didnt seem like we were removing the flag from "all" components just specific ones. If I mark it inactive it will affect "all". If we go that route we could split the flag out into two or more flags with more specific product/component combinations but then we have the issue of migration from the old one to the new one(s).
dkl
| Reporter | ||
Comment 4•14 years ago
|
||
(In reply to David Lawrence [:dkl] from comment #1)
> Here is the current list of product/component combinations that the
> needs-reconfig
> flag is visible for. Let me know which ones from the list you no longer need
> the
> flag.
I think we can drop the flag from them all. This flag was created for patches being handed over to RelEng for reconfigs, but as RelEng has changed our process, I believe these groups do not use these flags for anything else, and hence the flag can just be removed/disabled. (whatever is easiest for you).
> Product:Component
> -------------------------------
> Testing:General
> Testing:Infrastructure
> Testing:Mozmill
> Testing:New Frameworks
> Testing:Talos
ctalbert: ack?
> mozilla.org:MozillaBuild
ted: ack?
> mozilla.org:Release Engineering
> mozilla.org:Release Engineering: Custom Builds
yes, thats fine.
> One thing to note is that the flags will be removed from the current bugs
> under the product/component and will not be recoverable. Let me know if
> this is ok as well.
this is ok by me.
> dkl
Thanks
John.
Comment 5•14 years ago
|
||
The MozillaBuild component never needed this flag, so it's fine to remove it.
| Assignee | ||
Comment 6•14 years ago
|
||
(In reply to John O'Duinn [:joduinn] from comment #4)
> > Product:Component
> > -------------------------------
> > Testing:General
> > Testing:Infrastructure
> > Testing:Mozmill
> > Testing:New Frameworks
> > Testing:Talos
> ctalbert: ack?
Will wait for ctalbert to ack before moving forward.
dkl
(In reply to David Lawrence [:dkl] from comment #6)
> (In reply to John O'Duinn [:joduinn] from comment #4)
> > > Product:Component
> > > -------------------------------
> > > Testing:General
> > > Testing:Infrastructure
> > > Testing:Mozmill
> > > Testing:New Frameworks
> > > Testing:Talos
> > ctalbert: ack?
>
> Will wait for ctalbert to ack before moving forward.
Fine with us. Kill it.
| Assignee | ||
Comment 8•14 years ago
|
||
Done
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 9•14 years ago
|
||
(In reply to David Lawrence [:dkl] from comment #8)
> Done
sweet! thanks dkl!
You need to log in
before you can comment on or make changes to this bug.
Description
•