304661 - Offical branding is turned off

Status: RESOLVED INVALID

(Firefox Build System :: General, defect)

Description

[David B. Haun]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050814 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050814 Firefox/1.0+

Every time you View on branch builds you do not see offical branding.

Reproducible: Always

Steps to Reproduce:
1.Launch Firefox browser.


Actual Results:  
Shows unoffical branding

Expected Results:  
Shows offical branding

Should function the same with any Operating System.

Comment 1

[Jaime Mitchell (use [e-mail] for email)]

Thats because it has not be switched on yet -> Invalid.

There were never any plans to have it switched on yet, it may be enabled
sometime soon for firefox 1.5 beta.

Comment 2

[David B. Haun]

I feel resolution of invalid is not correct and should be review by Quality
Assurence.

Comment 3

[Mike Connor [:mconnor]]

As reported, this bug is completely invalid, since you're saying that its a bug.
 Its not.  At some point we will flip the branding, but not yet.

Comment 4

[chris hofmann]

we ought to turn offical branding on now to reduce moving parts and so we can start to do end-to-end check on stuff like https://bugzilla.mozilla.org/show_bug.cgi?id=350090

Comment 5

[Mike Beltzner [:beltzner, not reading bugmail]]

Flipping the official branding bit creates an official release. Until the firefox2 and mozilla181 blocker queues are clear, we don't have an official release, and should not be stating that we do.

Throughout the Firefox2 beta cycle we've been flipping this bit for the build that will become a release candidate for that official release. I don't see why that would change for the Firefox2 RCs.

I'd mark this INVALID as well, and definitely not blocking firefox2.

Comment 6

[Mike Connor [:mconnor]]

We shouldn't do this, as the official branding carries certain legal requirements with regard to various agreements that are in place.  This came up two weeks ago, and it was determined this was not in our best interests to use official branding on anything short of real candidate builds.  candidate l10n builds will be available (with official branding) sometime Monday.

I'm not sure why you'd reopen a year-old INVALID bug like this instead of filing something new, but that's not really the point either...