Closed
Bug 596139
Opened 14 years ago
Closed 14 years ago
Rename blocking2.0:beta6+ to blocking2.0:beta7+ (and create new beta6+)
Categories
(bugzilla.mozilla.org :: General, defect)
bugzilla.mozilla.org
General
Tracking
()
RESOLVED
FIXED
People
(Reporter: beltzner, Assigned: beltzner)
Details
https://bugzilla.mozilla.org/buglist.cgi?quicksearch=ALL%20blocking2.0:beta6+
Please change the value of cf_blocking_20 from beta6+ to beta7+ on all of those. Thanks!
Assignee | ||
Comment 2•14 years ago
|
||
Upping to blocker as this has remained unassigned as of yet.
Severity: critical → blocker
Assignee | ||
Comment 3•14 years ago
|
||
I can't make the severity knob go higher, no matter how hard I try. Maybe I can make a new severity level that will do this for me.
Comment 4•14 years ago
|
||
quick tip (just so you know for next time) : for something that's time-sensitive like this, you can make it page someone about the blocker status if you change the assignee to server-ops@mozilla-org.bugs
I have release blockers for the b6 release to deal with right now, but I'll hit this as soon as I get those dealt with. (if this is a release blocker, let me know, otherwise it's going to wait for the release stuff)
Assignee: nobody → justdave
Assignee | ||
Comment 5•14 years ago
|
||
Turns out I had the power to do this all along!
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•14 years ago
|
Assignee: justdave → beltzner
OS: Windows 7 → All
Hardware: x86 → All
Summary: please mass change all bugs marked blocking2.0:beta6+ to blocking2.0:beta7+ → Rename blocking2.0:beta6+ to blocking2.0:beta7+ (and create new beta6+)
Updated•13 years ago
|
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.
Description
•