Closed Bug 845947 Opened 11 years ago Closed 11 years ago

Firefox <=19.0 updates on betatest do not go passed Firefox 19.0

Categories

(Release Engineering :: Release Requests, defect)

All
Windows 8
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: u279076, Assigned: rail)

References

Details

Firefox versions on Windows 8 are not updating to 19.0.1 on betatest currently. They are receiving updates to 19.0 instead of 19.0.1. I've seen this both in automation and through manual testing.

Here are some sample URLs:
> https://aus3.mozilla.org/update/3/Firefox/19.0/20130215130331/WINNT_x86-msvc/de/betatest/Windows_NT%206.2/default/default/update.xml?force=1
> https://aus3.mozilla.org/update/3/Firefox/17.0/20121119183901/WINNT_x86-msvc/en-US/betatest/Windows_NT%206.2/default/default/update.xml?force=1
Just to be clear, desired behavior is:

* Win8: users on FF19.0 or earlier are updated to FF19.0.1
* Not Win8: users on FF18.0.2 or earlier are updated to FF19.0
Blocks: 844053
In bug 844053 we separated Win8 users for the release and releasetest channel only. Adding betatest to that exception would add more manual work for releng for every single beta release.

At the moment we can test the updates only on the releasetest channel which will be avalable only after push to mirrors.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
I'm going to modify the releasetest snippets so we can verify that updates work prior to push to mirrors.
Assignee: nobody → rail
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
(In reply to Rail Aliiev [:rail] from comment #3)
> I'm going to modify the releasetest snippets so we can verify that updates
> work prior to push to mirrors.

Confirmed the modified releasetest snippets are working:
* Windows 8 updates to 19.0.1
* All other platforms update to 19.0

Marking this resolved fixed based on this fact.
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.