If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Firefox beta doesn't identify itself as a beta

RESOLVED INVALID

Status

()

Firefox
General
RESOLVED INVALID
8 years ago
7 years ago

People

(Reporter: Eric Moore, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [CLOSEME 2011-1-30])

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2

I just ran "Help -> Check for updates" using Firefox 3.6.0 under Vista. The window said 3.6.2 was available, so I let it upgrade. "Help -> About Mozilla Firefox" identifies it as Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/[b]3.6.2[/b]

The only mention that its a beta is that AFTER I upgraded it opened a http://www.mozilla.com/en-US/firefox/3.6.2/whatsnew/ tab that says "Thanks for helping us beta test Firefox 3.6.2!" and later on mentions its beta3. I checked app.update.channel and it is set to beta. 

Why doesn't the beta identify itself as a beta? Its a beta, not a release candidate or a final release. I don't want to upgrade every time there is a beta, I just want the option. In this case there wasn't anything worth the risk (no interesting features, important security fixes or bug fixes that I cared about (the NYTimes article skimmer web page is still broken)), so I wouldn't have upgraded if I had known it was a beta.

http://www.mozilla.com/en-US/firefox/3.6.2/releasenotes/

Reproducible: Didn't try

Comment 1

8 years ago
This is expected on stable branches. Each beta is a release candidate meaning that if there are no problems found the exact build you are using will be shipped as 3.6.2.

If you want only get final release builds you can use https://addons.mozilla.org/en-US/firefox/addon/6263 to switch off the beta channel to the release channel.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INVALID
(Reporter)

Comment 2

8 years ago
Its always identified itself as a beta before. Re-opened. Show me where it is documented that every beta is a release candidate. I searched http://support.mozilla.com/en-US/kb/Firefox+Help?style_mode=inproduct and couldn't find anything that says that. Searching for "beta release candidate" for example, finds nothing.

Even if Mozilla wants to lie in the build id (its going to be wrong if you release a different build later on as the release) the window telling me that its available should identify it as a beta so that I can make a informed decision.

I explicitly said I wanted the option of upgrading to a beta build, I am merely complaining that it always used to tell me if it was a beta build and that information was useful.




.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---

Comment 3

8 years ago
Not in stable releases. It is an release candidate build, released to the stable beta update channel as there is no release candidate channel. The way Mozilla does releases a release candidate channel cannot exist.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago8 years ago
Resolution: --- → INVALID
(Reporter)

Comment 4

8 years ago
All that I'm talking about is the text in the notification window that gives you the appropriate context (i.e. did I get this update offer because I'm helping to test stuff or did I get it because they released a new version).

http://kb.mozillazine.org/Software_Update claims the beta channel gets "every beta, release candidate, and release version of the product". Is that incorrect? The reason why I'm asking is that is what I'm used to seeing, and I react differently depending upon whether its a released version or not.

I know what it used to do, I reported that the behavior changed, and you won't point me to some web page that shows that either Mozilla changed their mind or that I misunderstood the way it used to work - you just keep insisting that its working correctly. Please prove it. I'll be the first to admit I could be wrong, but the fact that you are a QA volunteer doesn't mean you're automatically right. 

I would appreciate it if you'd stop marking this bug report as resolved invalid until this conversation is finished.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]

Updated

7 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.