666407 - Turn off 3.5 builds

Status: VERIFIED FIXED

(Release Engineering :: General, defect, P3)

Description

[Chris AtLee [:catlee]]

Firefox 3.5 is EOLed. Once we get the o.k. from the powers-that-be, let's turn off nightlies, per-checkin builds, repacks and tests in our configs.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

And geriatric?

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

those will stop when the builds stop.  I dont see any reason to touch the geriatric master to remove a branch that isn't causing much load anyway.

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Agreed - I meant killing the master and slaves.  So this bug is just to stop the day-to-day builds, but retains capacity for releases?

Comment 4

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

Announced in today's MozillaFoundation, and last week's platform meeting. http://oduinn.com/blog/2011/06/27/stopping-firefox-3-5/

Comment 5

[John O'Duinn [:joduinn] (please use "needinfo?" flag)]

(In reply to comment #3)
> Agreed - I meant killing the master and slaves.  So this bug is just to stop
> the day-to-day builds, but retains capacity for releases?
Not quite. This stops *all* builds, including build-on-checkin, nightly builds and release builds. 

See details here: http://oduinn.com/blog/2011/06/27/stopping-firefox-3-5/




(In reply to comment #1)
> And geriatric?

(In reply to comment #2)
> those will stop when the builds stop.  I dont see any reason to touch the
> geriatric master to remove a branch that isn't causing much load anyway.
We need to keep geriatric master around until all the PPC and nonSSE2 needs go away. FF3.5 reduces, but does not eliminate, all jobs to geriatric master.

Comment 6

[John Ford [:jhford] CET/CEST Berlin Time]

(In reply to comment #5)
> (In reply to comment #1)
> > And geriatric?
> 
> (In reply to comment #2)
> > those will stop when the builds stop.  I dont see any reason to touch the
> > geriatric master to remove a branch that isn't causing much load anyway.
> We need to keep geriatric master around until all the PPC and nonSSE2 needs
> go away. FF3.5 reduces, but does not eliminate, all jobs to geriatric master.

Which by my interpretation of our system requirements page, is when we EOL Firefox 3.6.

ftr, the reason I have to interpret the sysreqs is that "recommended" is used to describe which CPUs our binaries support for Mac.  As we don't actually produce PPC binaries for 4.0, and Intel CPU is only a recommendation for 4.0, I think its reasonable to assert that those recommendations are in fact requirements.

http://www.mozilla.com/en-US/firefox/system-requirements.html

Windows
<snip>
Recommended Hardware
<snip>
    Pentium 4 or newer processor that supports SSE2
<snip>

Mac
<snip>
Recommended Hardware
    Macintosh computer with an Intel x86 processor
<snip>

Comment 7

[Chris AtLee [:catlee]]

Attachment: Turn off mozilla-1.9.1

We need to keep mozilla-1.9.1 alive on the build side of things so we can generate refreshed MUs for it.

Comment 8

[[e-mail] (:bhearsum)]

Comment on attachment 542576 [details] [diff] [review]
Turn off mozilla-1.9.1

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

Comment 9

[[e-mail] (:bhearsum)]

Comment on attachment 542576 [details] [diff] [review]
Turn off mozilla-1.9.1

Whoops, used the wrong field.

Comment 10

[Nick Thomas [:nthomas] (UTC+12)]

Comment on attachment 542576 [details] [diff] [review]
Turn off mozilla-1.9.1

There's also a 1.9.1 reference in mozilla-tests/production_config.py in BRANCHES that can go.

Comment 11

[Chris AtLee [:catlee]]

Attachment: refreshed patch

carrying forward r+
this has mozilla-1.9.1 references removed from master_common.py and mozilla-tests/production_config.py

Comment 12

[Nick Thomas [:nthomas] (UTC+12)]

This went into production on July 30th. I've removed the latest from firefox/nightly on ftp:
 latest-mozilla-1.9.1
 latest-mozilla-1.9.1-l10n
 latest-firefox-3.5.x       (symlink)
 latest-firefox-3.5.x-l10n  (symlink)
And emptied the nightly check files 
 Firefox_mozilla-1.9.1.txt
 XULRunner_mozilla-1.9.1.txt
in at cvs 
 mozilla/tools/tinderbox-configs/monitoring/

Also removed firefox/tinderbox-builds/mozilla-1.9.1*.

Comment 13

[Tony Mechelynck [:tonymec]]

VERIFIED. When I looked for the Fx mozilla-1.9.1 yesterday (well, earlier today by Mountain View clocks), they were nowhere to be found: the latest-mozilla-1.9.1 and -l10n directories have now disappeared.