Closed
Bug 1482106
Opened 7 years ago
Closed 7 years ago
Please enable gecko approval flags on attachments in Release Engineering:: Release Automation: Uploading
Categories
(bugzilla.mozilla.org :: Administration, task)
Tracking
()
RESOLVED
FIXED
People
(Reporter: Callek, Assigned: dkl)
References
Details
So I have a set of patches in Release Engineering::
Release Automation: Uploading that I can't request approval on.
I think we need the gecko "fixed/status" and patch-level "approval" flags enabled in that component.
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•7 years ago
|
||
(In reply to Justin Wood (:Callek) from comment #0)
> So I have a set of patches in Release Engineering::
> Release Automation: Uploading that I can't request approval on.
>
> I think we need the gecko "fixed/status" and patch-level "approval" flags
> enabled in that component.
I have added the patch level approval flags. What exactly are the gecko fixed/status flags you need added? Do you have a product/component combo where they currently are displayed that I can use as reference?
dkl
Flags: needinfo?(bugspam.Callek)
Reporter | ||
Comment 2•7 years ago
|
||
(In reply to David Lawrence [:dkl] from comment #1)
> (In reply to Justin Wood (:Callek) from comment #0)
> > So I have a set of patches in Release Engineering::
> > Release Automation: Uploading that I can't request approval on.
> >
> > I think we need the gecko "fixed/status" and patch-level "approval" flags
> > enabled in that component.
>
> I have added the patch level approval flags. What exactly are the gecko
> fixed/status flags you need added? Do you have a product/component combo
> where they currently are displayed that I can use as reference?
I was thinking the "Firefox Tracking Flags" section
Firefox Build System::Task Configuration
Flags: needinfo?(bugspam.Callek)
Assignee | ||
Comment 3•7 years ago
|
||
Should be good to go now then.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•