Closed Bug 952895 Opened 10 years ago Closed 10 years ago
Yandex partner repack changes for Fx 27 release
Please update Yandex toolbar version to the following http://yadi.sk/d/mGZy11VkEmHuy http://yadi.sk/d/4A37GT4nEmHvk http://yadi.sk/d/Jx-PU-xaEmHwy http://yadi.sk/d/pixCxXZUEmHyF http://yadi.sk/d/7Bv4Y_alEmHzU http://yadi.sk/d/uWoQCCt4EmJ2R No essential changes in funtionality, general bug fixes and optimization
Assignee: nobody → mconnor
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
So far so good, will land when I'm in the office tomorrow.
https://hg.mozilla.org/build/partner-repacks/rev/8f33d546588b https://hg.mozilla.org/build/partner-repacks/rev/e5599191b04a https://hg.mozilla.org/build/partner-repacks/rev/dbb533f99592 https://hg.mozilla.org/build/partner-repacks/rev/d4078b2f2265 https://hg.mozilla.org/build/partner-repacks/rev/3708bc7134c9 https://hg.mozilla.org/build/partner-repacks/rev/4a05be4b5eac Coop/Ben/Rail: Given the multiple go-rounds last time, can you guys let me know when we get a beta build out with these changes, so I can let Galina know for testing?
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
The changes will be available in the next beta which ships this Friday.
Rail, are the beta partner builds by default available at some special place or should we wait for direct links here as we do for release builds?
We publish partner repacks as a part of beta builds regularly (usually Tue and Fri) using latest changes from http://hg.mozilla.org/build/partner-repacks/. You can found them at http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/ -- browse to the latest versioned directory, e.g. http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/27.0b8-candidates/build1/partner-repacks/
What about release builds?
The release candidates are at http://ftp.mozilla.org/pub/mozilla.org/firefox/candidates/27.0-candidates/build1/partner-repacks/ and will be copied to http://ftp.mozilla.org/pub/mozilla.org/firefox/releases/27.0/partner-repacks/ at some point today once QA signs off.
You need to log in before you can comment on or make changes to this bug.