317103 - Firefox on 'release' Channel should not be updated to a Release Candidate

Status: RESOLVED INVALID

(AUS Graveyard :: General, defect)

Description

[Stebs]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051118 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051118 Firefox/1.5

The Release Candidates for Firefox 1.5 where available with the Update-Channel set to 'release'.
Something has to be done so that the final Firefox 1.5 does not update itself to a future Release Candidate, for example restricting the release-channel for the real Release (even if that means a last modification has to be done to an RC taken as final Release).

Reproducible: Always

Comment 1

[Reed Loden [:reed]]

-> AUS, as Firefox itself would have nothing to do with this.

Comment 2

[u88484]

um ya it should because its a release candidate where as with 1.5 RC3 that became 1.5 final and there was no need to update again.

Comment 3

[Reed Loden [:reed]]

Heh, I just noticed your Gecko build is from 20051118. Firefox 1.5 final (which is the same thing as RC3) was built on 20051111. To get to 20051118, you would have to be on the nightly channel.

Comment 4

[Reed Loden [:reed]]

(In reply to comment #2)
> um ya it should because its a release candidate where as with 1.5 RC3 that
> became 1.5 final and there was no need to update again.

According to the Change Update Channel extension's comments about each channel, "release" should only contain stable release versions including security updates, while "beta" should contain beta, release candidate, release, and security updates. I'm not sure if that text is authoritive, but that's just what it says. :)

Comment 5

[Stebs]

(In reply to comment #3)
> Heh, I just noticed your Gecko build is from 20051118. Firefox 1.5 final (which
> is the same thing as RC3) was built on 20051111. To get to 20051118, you would
> have to be on the nightly channel.
> 
Sure, always was on nightly (since early 0.8 days) and in fact was never confused or fooled MYSELF by RCs beeing on the Release Channel ;)

(In reply to comment #4)
> 
> According to the Change Update Channel extension's comments about each channel,
> "release" should only contain stable release versions including security
> updates, while "beta" should contain beta, release candidate, release, and
> security updates. I'm not sure if that text is authoritive, but that's just
> what it says. :)

Thats exactly what this Bug is about: This "rule" ("release" should only contain stable release versions including security updates) was not followed with RCs for Fx 1.5. That was ok since FF 1.0 did not have any Channel Update System, but  now with 1.5 out, it's not ok anymore.

So this Bug is really only a "reminder" that in future, the rule must be followed, else normal Users will get RCs, thats's all.

Thanks btw for switching this to AUS (if that is really the right component for the Channel setting in channel-prefs.js)  

Comment 6

[timeless]

*** This bug has been confirmed by popular vote. ***

Comment 7

[Stebs]

I think the time has come to close this as invalid!?
Heard of no problems concerning Updates to an Release Candidate.
Waited for an sucessful (regular) update from 1.5 to 2.0 and now I think that I can just close this Bug...