Closed Bug 672421 Opened 14 years ago Closed 14 years ago

Categories

(Release Engineering :: General, defect)

x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 659552

People

(Reporter: dholbert, Unassigned)

References

()

Details

STEPS TO REPRODUCE: 1. Download the current latest "mozilla-beta-linux" tinderbox-build, from ftp://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-beta-linux/1311015931/firefox-6.0.en-US.linux-i686.tar.bz2 (this is the latest mozilla-beta-linux build available at the moment) 2. Run it. Visit about:buildconfig ACTUAL RESULTS: The browser has "Aurora" branding, even though about:buildconfig shows that it's "Built from http://hg.mozilla.org/releases/mozilla-beta/rev/65ed6316d72d " EXPECTED RESULTS: Firefox branding Confirmed on latest mozilla-beta-win32 build, too.
I discovered this when trying to find archived beta builds that we've shipped to beta users (to debug a crash report from the beta channel). I was directed to the above directory, as a place where I could download these beta builds. If I should be looking somewhere else, please let me know.
(In reply to comment #1) > I was directed to the above directory, as a place where I could download > these beta builds. If I should be looking somewhere else, please let me > know. Found out in #build that the official/released beta builds are here: http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/6.0b2-candidates/ I think this bug is still valid, though -- it's confusing to generate beta builds with aurora branding. Maybe they shouldn't get official branding -- perhaps something else (nightly?) -- but they also shouldn't get the Aurora-channel-specific branding when the code has been post-Aurora for weeks.
This is the slightly untidy result of the way we're doing builds for the beta channel. As you say, the actual builds for releasing end up in firefox/nightly/6.0bN-candidates/ for QA purposes, and are copied to firefox/releases/6.0bN/ for end users (use ftp://ftp.m.o to see them). These come from runs of the release automation previously used for 4.0*, 3.6*, etc. They have Firefox branding. We also need to create builds when people land in mozilla-beta, and they end up in firefox/tinderbox-builds/. They don't have Firefox branding because of a long standing policy of not creating any development builds which look like official builds. I agree Aurora branding isn't great, and we've used the codenames like Gran Paradiso in the past instead.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.