Closed Bug 407970 Opened 18 years ago Closed 15 years ago

Tech evangelism bugs can't block a release

Categories

(bugzilla.mozilla.org :: General, defect)

Product:
bugzilla.mozilla.org
Component:
General
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: martijn.martijn, Assigned: gerv)

Details

(Whiteboard: bmo4.0-resolved)

See discussion in bug 407636. Some tech evangelism bugs are really serious and were caused by some technical change in trunk builds. I think some tech evangelism bugs are that serious that it should be possible to block the current release for it (which is 1.9 currently).
Assignee: justdave → marcia
Component: Bugzilla: Other b.m.o Issues → Bugzilla: Keywords & Components
OS: Windows XP → All
QA Contact: reed → timeless
Hardware: PC → All
In theory this sounds reasonable, and we can add the blocking flag to the tech evangelism component which is what I think you are asking for. On the flip side, this might mean we get more nominations than we normally would.
Status: NEW → ASSIGNED
See also bug 584138, which exists solely to be a blocker proxy for bug 583914, since TE bugs still don't have Gecko release flags available.
Fixed in bmo-4.0 branch; Firefox cf_blocking_* and cf_status_* (but not the ones for fennec, Thunderbird or SeaMonkey, unless you tell me otherwise) will be available in every component in the TE product. Gerv
Whiteboard: bmo4.0-resolved
Assignee: mozillamarcia.knous → gerv
Component: Bugzilla: Keywords & Components → Bugzilla: Other b.m.o Issues
QA Contact: timeless → other-bmo-issues
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Component: Bugzilla: Other b.m.o Issues → General
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.