We are planning to remove support for Mac OS X 10.5 in Firefox 17. We shouldn't update any users on Mac OS X 10.5 to Firefox 17.
Per http://en.wikipedia.org/wiki/Darwin_%28operating_system%29#Release_history this means blocking 'Darwin 9.*'
Created attachment 640908 [details] [diff] [review] [cvs] Block 'Darwin 9'
Hmm. Isn't Firefox 17 going to be the next ESR? Won't it make more sense to remove support *after* 17? Also I don't remember any official conclusion to the discussion in mozilla.dev.planning on this particular topic.
There's a big thread about this in the newsgroups. https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.platform/aT7hy7YDdqA Please have a read of that and follow up there.
Comment on attachment 640908 [details] [diff] [review] [cvs] Block 'Darwin 9' Checking in config-dist.php; /cvsroot/mozilla/webtools/aus/xml/inc/config-dist.php,v <-- config-dist.php new revision: 1.218; previous revision: 1.217 done Will test in staging before asking IT to deploy.
Worked as expected in blocking a faked update to FF17.0a1 to a 10.5.8 machine. $ cvs tag AUS2_PRODUCTION config-dist.php W config-dist.php : AUS2_PRODUCTION already exists on version 1.217 : NOT MOVING tag to version 1.218 $ cvs tag -F AUS2_PRODUCTION config-dist.php T config-dist.php
Sorry about removing the blocking relation.
If updates are disabled for Mac OS X 10.5 users now I'll go ahead and land the patch that will make the build not run on Mac OS X 10.5. Is this the case?
Working fine if I adjust requests: 10.6.8 gets an update to 17.0a1: https://aus3.mozilla.org/update/3/Firefox/16.0a1/20120716042007/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/nightly/Darwin%2010.8.0/default/default/update.xml?force=1 10.5.8 doesn't: https://aus3.mozilla.org/update/3/Firefox/16.0a1/20120716042007/Darwin_x86_64-gcc3-u-i386-x86_64/en-US/nightly/Darwin%209.8.0/default/default/update.xml?force=1