gecko-dev/testing/release
rhelmer%mozilla.com 6130518030 better error reporting 2006-08-01 21:57:18 +00:00
..
common split line in proper place 2006-08-01 21:48:17 +00:00
l10n
updates better error reporting 2006-08-01 21:57:18 +00:00
README.txt

README.txt

Mozilla Build Verification Scripts
---

--
Contents
--

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

--
Update verification
--

verify_aus.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.

  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

  This is really just a thin wrapper around the common/download_mars.sh 
  functionality.

verify_updates.sh 
  downloads two consecutive releases, downloads the partial MAR for the older
  release (using the technique described for verify_aus.sh), applies the
  MAR to the older release, and compares the two releases.

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

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

--
l10n verification
2A
--

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.