If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Add flags to mozilla.org :: Build & Release

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Administration
RESOLVED FIXED
10 years ago
6 years ago

People

(Reporter: nthomas, Assigned: reed)

Tracking

Details

(Reporter)

Description

10 years ago
I'm requesting the addition of
  * blocking1.9 and wanted1.9 flags for bugs
  * approval1.9 for patches
in the Build & Release component of the mozilla.org product.
(Assignee)

Updated

10 years ago
Assignee: marcia → reed
(Assignee)

Comment 1

10 years ago
So, I've done this, but why exactly can't the patches be in an appropriate Firefox/Core component?
Status: NEW → ASSIGNED
Summary: Add flags to mozilla.org::Build&Release → Add flags to mozilla.org :: Build & Release
Sometimes we have build infrastructure work that could block a release. So a build infrastructure bug, filed correctly under Build&Release, would need these flags.
(Assignee)

Comment 3

10 years ago
Yeah, I understand blocking1.9/wanted1.9, but why do you need approval1.9 under Build & Release?
(Reporter)

Comment 4

10 years ago
Because it's annoying to have to farm out fixes into other bugs. Eg for the major update test, I think you're implying that all packaging fixes should be done in Firefox::Build Config. With appropriate checkin comments, I really don't think this is necessary.
(Assignee)

Comment 5

10 years ago
Ok.
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.