Firefox 4-9 should never update past FF12 (and same for Thunderbird)

RESOLVED FIXED

Status

P2
normal
RESOLVED FIXED
6 years ago
5 years ago

People

(Reporter: akeybl, Assigned: nthomas)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(4 attachments)

(Reporter)

Description

6 years ago
Because Win2K and WinXP SP 1 users on older versions of Firefox will never be updated to FF13, we need to push them to FF12 indefinitely such that they receive the desupport add-on hotfix/billboard. Those that can update past FF12 will do so within a couple of days.

tl;dr When FF13 is released on 6/5, FF4-9 should still update to FF12 (from then on).
(Assignee)

Updated

6 years ago
Assignee: nobody → nrthomas
Priority: -- → P2
(Assignee)

Comment 1

6 years ago
Created attachment 628458 [details] [diff] [review]
[cvs] drop older releases from sequence

This will mean we only generate snippets for 10.0+ to latest. Any preference for what we do about update verify ? We could check that 4-9 can update to 12 each release, or just drop them from the verify config.
Attachment #628458 - Flags: review?(bhearsum)
(Reporter)

Comment 2

6 years ago
It'd be preferable that we verify on each release if it isn't too much extra work.
Comment on attachment 628458 [details] [diff] [review]
[cvs] drop older releases from sequence

Review of attachment 628458 [details] [diff] [review]:
-----------------------------------------------------------------

It seems like a waste of machine time to me to continue to run update verify on these versions - we'd be doing the exact same tests over and over. If we really want to do it, we'll have to remove the "full" tests, because they'll end up trying to compare themselves against whatever the latest version is.
Attachment #628458 - Flags: review?(bhearsum) → review+
(Assignee)

Comment 4

6 years ago
Comment on attachment 628458 [details] [diff] [review]
[cvs] drop older releases from sequence

Checking in mozRelease-branch-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/mozRelease-branch-patcher2.cfg,v  <--  mozRelease-branch-patcher2.cfg
new revision: 1.30; previous revision: 1.29
done
Attachment #628458 - Flags: checked-in+
(Assignee)

Comment 5

6 years ago
We could probably do something like 

diff --git a/release/updates/mozRelease-firefox-win32.cfg b/release/updates/mozRelease-firefox-win32.cfg
--- a/release/updates/mozRelease-firefox-win32.cfg
+++ b/release/updates/mozRelease-firefox-win32.cfg
@@ -16,1 +16,1 @@ release="10.0" product="Firefox" platfor
-release="9.0.1" product="Firefox" platform="WINNT_x86-msvc" build_id="20111220165912" locales="de en-US ru" channel="betatest" from="/firefox/releases/9.0.1/win32/%locale%/Firefox Setup 9.0.1.exe"
+release="9.0.1" product="Firefox" platform="WINNT_x86-msvc" build_id="20111220165912" locales="de en-US ru" channel="betatest" from="/firefox/releases/9.0.1/win32/%locale%/Firefox Setup 9.0.1.exe" to="/firefox/nightly/12.0-candidates/build1/win32/%locale%/Firefox Setup 12.0.exe"

ie, add a 12.0 'to' var at the first old release, if we wanted to keep testing (but maybe chunking makes that not possible?). But I think it would be sufficient to check that bouncer links for 12.0 are still working - ideally just a HEAD request but that's not possible in the current framework, so we'd query AUS then download the mar file.

Updated

6 years ago
Status: NEW → ASSIGNED
(Assignee)

Comment 6

6 years ago
Created attachment 628650 [details] [diff] [review]
[tools] update verify configs - disabling full checks

In a perfect world we'd do fx4-9.0.1 in final verification only, or at least only in test mode only for update verify (a curl -I style HEAD request to bouncer). This is the expedient solution for now. I can make the locale lists alpha-sorted if you want, it was an attempt to make the diff less hideous but I'm not sure it worked.
Attachment #628650 - Flags: review?(bhearsum)
(Assignee)

Comment 7

6 years ago
TB is in too:

<Standard8> so if I'm on TB 7 and win2k and we publish an update to TB 13, then I won't get updated to 12?
	ouch
	yeah, we should do that
Summary: Firefox 4-9 should never update past FF12 → Firefox 4-9 should never update past FF12 (and same for Thunderbird)
(Assignee)

Comment 8

6 years ago
Created attachment 628651 [details] [diff] [review]
[cvs] drop older TB releases from sequence
Attachment #628651 - Flags: review?(mbanner)

Comment 9

6 years ago
Seamonkey?
I think they are still on older compiler so maybe they still support the systems mentioned here.
(Assignee)

Comment 10

6 years ago
Created attachment 628654 [details] [diff] [review]
[tools] update verify configs - disabling full checks for TB

Same again for TB - remove the full checks and paste in de en-US ru into the quick checks.
Attachment #628654 - Flags: review?(mbanner)
(Assignee)

Comment 11

6 years ago
(In reply to :aceman from comment #9)
> Seamonkey?
> I think they are still on older compiler so maybe they still support the
> systems mentioned here.

Actually, SeaMonkey releases are handled separately by that community. Thunderbird is include because they recently transitioned to using the same MoCo release-infrastructure as Firefox.
Comment on attachment 628650 [details] [diff] [review]
[tools] update verify configs - disabling full checks

Review of attachment 628650 [details] [diff] [review]:
-----------------------------------------------------------------

I agree that this is the best solution we have right now.
Attachment #628650 - Flags: review?(bhearsum) → review+
Attachment #628651 - Flags: review?(mbanner) → review+
Comment on attachment 628654 [details] [diff] [review]
[tools] update verify configs - disabling full checks for TB

This looks fine, but I'm going to defer on complexity of reading/checking.
Attachment #628654 - Flags: review?(mbanner) → review?(bhearsum)
Attachment #628654 - Flags: review?(bhearsum) → review+
(Assignee)

Comment 14

6 years ago
Comment on attachment 628650 [details] [diff] [review]
[tools] update verify configs - disabling full checks

http://hg.mozilla.org/build/tools/rev/e11a2673c6bd
Attachment #628650 - Flags: checked-in+
(Assignee)

Comment 15

6 years ago
Comment on attachment 628651 [details] [diff] [review]
[cvs] drop older TB releases from sequence

Checking in mozRelease-thunderbird-branch-patcher2.cfg;
/cvsroot/mozilla/tools/patcher-configs/mozRelease-thunderbird-branch-patcher2.cfg,v  <--  mozRelease-thunderbird-branch-patcher2.cfg
new revision: 1.33; previous revision: 1.32
done
Attachment #628651 - Flags: checked-in+
(Assignee)

Comment 16

6 years ago
Comment on attachment 628654 [details] [diff] [review]
[tools] update verify configs - disabling full checks for TB

http://hg.mozilla.org/build/tools/rev/64a403268632
Attachment #628654 - Flags: checked-in+
(Assignee)

Updated

6 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
(Assignee)

Updated

6 years ago
Blocks: 744598
For the purposes of verifying this bug, I'll add a couple 4-9 builds into the 13RC update checks.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.