Closed
Bug 1221205
Opened 9 years ago
Closed 9 years ago
Stop showing /whatsnew in Developer Edition 44
Categories
(Release Engineering :: Release Requests, defect)
Release Engineering
Release Requests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Unassigned)
References
Details
(Whiteboard: [fall-2015-engagement])
+++ This bug was initially created as a clone of Bug #1196530 +++
Backing out changes from bug 1196530 should be sufficient. Should be done before the next merge day or anytime we want this.
Comment 1•9 years ago
|
||
putting this against 1206668 just so we address it before next merge
Blocks: 1206668
Comment 2•9 years ago
|
||
I'm not sure we need to do anything here, at least not on a precise timetable.
On m-c the aurora branding doesn't set an url (http://hg.mozilla.org/mozilla-central/file/default/browser/branding/aurora/pref/firefox-branding.js), so the next merge to aurora will be fine. The aurora branding won't be enabled once we merge current aurora to beta or higher. So worst case if we leave it - vestigial config that's never exercised. A teeny tiny footgun.
You need to log in
before you can comment on or make changes to this bug.
Description
•