Closed
Bug 1207522
Opened 10 years ago
Closed 10 years ago
Firefox Beta 41.0b9 updates to Firefox 41.0 instead of to 42.0b1
Categories
(Release Engineering :: Release Requests, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: quicksaver, Unassigned)
Details
STR:
1. Install Firefox Beta 41.0b9 [1] (41.0b8 also has this problem, haven't tried any others)
2. Start it up
3. Open About dialog, update it, restart it
If I go to the About dialog again, it will say it's on version 41.0, although it still says it's in the beta channel. I confirmed through about:buildconfig it's the same build as the 41.0 actual release, while 42.0b1 is a different build.
I would have expected it to update to 42.0b1, and it won't update automatically to it. Is this expected for the first beta release of each cycle? I had never noticed it before.
As expected, Nightly updated correctly to 44.0a1 as soon as it was available, and Dev.Edition (Aurora) is still on 42.0a2 as there isn't a 43.0a2 build yet.
[1] http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/41.0b9/
Comment 1•10 years ago
|
||
It just hasn't shipped yet, even though you see it in firefox/releases/42.0b1/ on the ftp server. The canonical place to check is at https://www.mozilla.org/en-US/firefox/channel/, and hover over the download box.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Comment 2•10 years ago
|
||
(In reply to Luís Miguel [:quicksaver] from comment #0)
> As expected, Nightly updated correctly to 44.0a1 as soon as it was
> available, and Dev.Edition (Aurora) is still on 42.0a2 as there isn't a
> 43.0a2 build yet.
Aurora goes through an extended QA period before we turn updates on again. Could be end of this week, or early next week, before that happens.
| Reporter | ||
Comment 3•10 years ago
|
||
Thank you for the info, I see the logic in the update process. I'm sorry for the false alarm.
Comment 4•10 years ago
|
||
No worries. And thanks for filing a bug. It's better to be false alarmed rather than having something broken. :)
You need to log in
before you can comment on or make changes to this bug.
Description
•