Firefox 34.0



  1. Firefox 34.0 Download
  2. Mozilla Firefox 34.0 Free Download
< Releases

Choose which Firefox Browser to download in your language Everyone deserves access to the internet — your language should never be a barrier. That’s why — with the help of dedicated volunteers around the world — we make the Firefox Browser available in more than 90 languages. Mozilla Firefox Description. Mozilla Firefox is a free, fast and efficient cross-platform web browser and one of the most popular browsers in use. Firefox boasts speed and tabbed.

  • 1Firefox 34.0 build1
    • 1.3Updates for beta
      • 1.3.1Update verify
  • 2Firefox 34.0 build2
    • 2.3Updates for beta
      • 2.3.1Update verify
  • 4Fennec 34.0 build1
  • 5Fennec 34.0 build2
  • 6Fennec 34.0 build3

Checklist

  • (RelMan) Ship the l10n milestone
  • (RelMan) Submit to Ship It
  • Updates for beta - prep done, waiting to be able to test
  • Started build2 (prior to shipping to beta channel)

Issues

  • a single locale, ta, has failed in chunk 9/10 win32, restarted standalone repack (bad slave/disk space issue?), triggered release-mozilla-release-win32_repack_complete manually

Updates for beta

cf 33.0 notes

  • partial from 34.0b11 generated at build time (from this patch)
  • release blob looks good
  • added bouncer product/locations for beta-cdntest/beta:

Update verify

Prep

On nthomas' laptop, after en-US builds done:

Attached to bug 1071606 as attachment 8528267.

Running tests

Rather than grabbing 3 slaves and running these manually, we may be able to twist the automation's arm:

  • wait until we get the 'updates available on betatest' email
  • commit the config patch to tools (no fallout from this on next release)
  • force the beta update verify jobs (eg release-mozilla-beta-linux_update_verify_1/6). We'd need to set the script_repo_revision property to the revision when that landed

The emails we get back would be labelled 34.0b11, but I don't think it's worth bumping the release config and reconfiging just to avoid that.

--> Turns out this doesn't work, script_repo_revision was still set to FIREFOX_34_0b11_RELEASE_RUNTIME.

Checklist

  • (RelMan) Ship the l10n milestone
  • (RelMan) Submit to Ship It
  • Push to mirrors(hwine)

Issues

Download
  • didn't need to modify extraPartials, as we didn't ship build1 to beta channel
  • linux64 partner repack hit a 500 error grabbing pkg-dmg from hg.m.o, rebuild
  • the sendchange for 34.0.5 matched the schedulers for build2, firing some extra builds
    • tagging, which moved the release tags on m-r, and was up to te on locales before being cancelled. Remediated by putting m-r back on 456394191c90 - changeset
    • schedulers, the reset job ran, and it would be very helpful if things just worked come release time. See Releases/Firefox_34.0/BuildNotes#Fix scheduling for resolution.
  • first 2 final verifies (after mirror push) failed due to issues with aus3. (First run, 1 failure; second run, 4 failures; third run passed.)
    • contacted gozer in #webops who will double check for any issues that may impact us Monday

Updates for beta

  • partial from 34.0b11 generated at build time (from this patch)
  • release blob looks good
  • modified the bouncer locations for Firefox-34.0-Partial-34.0b11 to s/build1/build2/

Update verify

Prep

On nthomas' laptop, after en-US builds done:

Attached to bug 1071606 as attachment 8528998.

In Balrog, updated beta-localtest and beta-cdntest rules to point at Firefox-34.0-build2.

Notice we have a problem with the complete's not being available (locations are in releases/ dir), filed bug 1105228 to handle creating a new blob to point to. bhearsum landed that in Balrog, and set up new Firefox-34.0build2-Complete product & locations in candidates dir.

There was some confusion about whatsnew pages. We wanted them for en-US, and set up another blob (Firefox-34.0-build2-beta-2-whatsnew) which included action and openURL. We then discovered that the in-app code only uses that when the app version is changing, so the rules part was undone.

Running tests

Reverting to manual checks.

On b-linux64-hp-021 (screen 0 is linux32, screen 1 is linux64), bld-lion-r5-072, b-2008-ix-0082. Adjust to right config for platform:

Results: expected differences in channel-prefs.js and update-settings.ini, no failures:

Push to beta

bhearsum updated the rule directly in Balrog, changing the mapping to Firefox-34.0-build2-beta.

Fix scheduling

Because we hit an issue when 34.0.5 started 34.0 tagging what reset the schedulers, scheduling fix required:

Post release

Firefox 34.0 Download

We're using the 34.0.5 post release to get the installers in the right place, and don't want the latest symlink to be updated to 34.0, so do this by hand:

More scheduler fallout

checksums, check permissions, and antivirus builders never ran

  • ran checksums by forcing the job, manually copy files over
  • did permissions checks by hand
  • forced antivirus job

build notes here

Firefox 34.0 download filehippo

Checklist

  • (RelMan) Ship the l10n milestone
  • (RelMan) Submit to Ship It
  • Started build2 for l10n fixes

Issues

  • android repacks all failed in configure with java < 1.7, we missed bug 1082325. Patch landed, updated tags and re-triggered jobs, all green.
  • email '[release] Fennec 34.0 build1: Updates available on None' with content 'Updates to Fennec 34.0 build1 are now ready for testing on the None channel.' Commented on bug 1019724.

Checklist

  • (RelMan) Ship the l10n milestone
  • (RelMan) Submit to Ship It
  • Doing a build3

Issues

  • None

Took the fix for sendchanges before starting this off.

Firefox

Checklist

  • (RelMan) Ship the l10n milestone
  • (RelMan) Submit to Ship It

Issues

None.

Mozilla Firefox 34.0 Free Download

This is done as the 31.3.0esr release. Tracked here

34.0
Retrieved from 'https://wiki.mozilla.org/index.php?title=Releases/Firefox_34.0/BuildNotes&oldid=1038835'




Comments are closed.