testing/release/README.txt
author Randell Jesup <rjesup@jesup.org>
Thu, 05 Sep 2013 15:34:05 -0400
changeset 258563 447a856a89bf457e621e93cdb9536ab7c52764a8
parent 1 9b2a99adc05e53cd4010de512f50118594756650
permissions -rw-r--r--
Bug 899159: (beta 24 version) clean up record issues in webrtc OpenSLES code + wallpaper r=padenot,derf,mwu a=bajaj on a CLOSED TREE

Mozilla Build Verification Scripts
---

--
Contents
--

updates -> AUS and update verification
l10n    -> l10n vs. en-US verification
common  -> useful utility scripts

--
Update verification
--

verify.sh
  does a low-level check of all advertised MAR files. Expects to have a
  file named all-locales, but does not (yet) handle platform exceptions, so 
  these should be removed from the locales file.

  prints errors on both STDOUT and STDIN, the intention is to run the
  script with STDOUT redirected to an output log. If there is not output
  on the console and an exit code of 0 then all tests pass; otherwise one
  or more tests failed.

  Does the following:

  1) download update.xml from AUS for a particular release
  2) download the partial and full mar advertised
  3) check that the partial and full match the advertised size and sha1sum
  4) downloads the latest release, and an older release
  5) applies MAR to the older release, and compares the two releases.
  
  Step 5 is repeated for both the complete and partial MAR.

  Expects to have an updates.cfg file, describing all releases to try updating 
  from.

-
Valid Platforms for AUS
-
Linux_x86-gcc3
Darwin_Universal-gcc3
Linux_x86-gcc3
WINNT_x86-msvc
Darwin_ppc-gcc3

--
l10n verification
--

verify_l10n.sh
  unpacks an en-US build for a particular release/platform, and
  then unpacks and compares all locales for that particular release/platform.

  Expects to have a file named all-locales, but does not (yet) handle platform 
  exceptions, so these should be removed from the locales file.

  Best practice is to take a directory full of diffs for a particular release
  and compare to a directory full of diffs for the current release, to see
  what l10n changes have occurred. For maintenance releases, this should
  be slim to none.