Closed
Bug 1478331
Opened 7 years ago
Closed 6 years ago
should nightly-asan-reporter builds use "nightly" branding instead of "unofficial"?
Categories
(Firefox Build System :: General, enhancement)
Firefox Build System
General
Tracking
(firefox71 fixed)
RESOLVED
FIXED
mozilla71
| Tracking | Status | |
|---|---|---|
| firefox71 | --- | fixed |
People
(Reporter: jcristau, Assigned: jcristau)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
I've noticed that some prefs differ between the nigthly-asan and regular nightly builds, that afaict are related to using browser/branding/unofficial instead of browser/branding/nightly. Is that what we want? E.g. regular nightly checks for updates more often, and has a firstrun and whatsnew page setting.
Comment 1•7 years ago
|
||
The nightly branding is not specified in the mozconfig for nightly asan builds so it defaults to the unofficial branding. I'm not sure what the requirements are to use nightly branding, will find out.
Comment 2•7 years ago
|
||
:pdol do you have any objections to using the nightly branding in nightly asan builds?
Flags: needinfo?(pdolanjski)
Comment 3•7 years ago
|
||
No objection. My only concern is around having users not know this is the build they have, so as long as we don't have ways for users to get this version that aren't obviously labeled as a special build, I think using branding is fine.
Flags: needinfo?(pdolanjski)
| Assignee | ||
Comment 4•6 years ago
|
||
| Assignee | ||
Updated•6 years ago
|
Assignee: nobody → jcristau
Status: NEW → ASSIGNED
| Assignee | ||
Comment 5•6 years ago
|
||
Pushed by jcristau@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/b09fafd3deae
use nightly branding for ASan Nightly builds. r=dmajor
https://hg.mozilla.org/integration/autoland/rev/b919062c2b51
Include common-opt mozconfig from nightly-asan-reporter instead of duplicating much of it. r=dmajor
Comment 7•6 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/b09fafd3deae
https://hg.mozilla.org/mozilla-central/rev/b919062c2b51
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
You need to log in
before you can comment on or make changes to this bug.
Description
•