Mac daily builds: format & file names

[J.J. Enser]

Starting November 1st, the daily mac builds are delivered in the
following format:

MacOS 8/9:
mozilla bits:
. MacMozillaInstaller.sea.bin -> installer stub (~250K)
. MacMozillaFullInstall.sea.bin -> installer "blob" (~ 13MB,
includes all installer modules)
netscape bits:
. MacNetscape6Installer.sea.bin
. MacNS6FullInstaller.sea.bin

MacOS X:
. Mozilla-macosX-trunk.sea.bin -> mozilla disk image
. Netscape6-macosX.smi.bin -> netscape disk image

The Release Team no longer distributes the old "raw" packages, known as
'mozilla-mac{osx}.sit.bin' for Mozilla and 'netscape-mac{osx}.sit.bin'
for Netscape.

Distributing mac builds in 2 different forms has caused extra work for
developers & release engineering, as well as confusion for QA and
external contributors, while everybody needs to focus on the packaging
format we actually use for shipping both Mozilla and Netscape products
(which is the installer for OS9 and the disk image for OSX).

Note that only the upload of the "raw" bits has been turned off. The
actual packages are still produced by our daily automation, kept on the
build systems, and can be made available upon request whenever the
installer is broken and people need to get a hold of the daily build
before the problem gets fixed.
Such requests should be sent to the build engineer of the day (found on
the seamonkey tinderbox page)

More changes will come soon in an effort to standardize the file names
between platforms, between releases, and between products (Mozilla vs.
Netscape).

Stay tuned for more news and let me know if you have any questions.

--
J.J. Enser <mailto:j...@netscape.com>
CPD Release Engineering
Netscape Communications
--

[Gervase Markham]

> The Release Team no longer distributes the old "raw" packages, known as
> 'mozilla-mac{osx}.sit.bin' for Mozilla and 'netscape-mac{osx}.sit.bin'
> for Netscape.

This is somewhat of a problem: Patch Maker
(http://www.mozilla.org/hacking/patch-maker/) uses the sit builds on
OS/X. As I don't have an OS/X box (the instructions came from others) I
don't know if it's possible to use a disk image. Does the disk image
have an accessible chrome directory with the standard structure?

> Note that only the upload of the "raw" bits has been turned off. The
> actual packages are still produced by our daily automation, kept on the
> build systems, and can be made available upon request whenever the
> installer is broken and people need to get a hold of the daily build
> before the problem gets fixed.

Could we, instead of stopping build upload, put the builds in a
subdirectory of /latest/ or something? Or name them so the difference is
more clear?

> More changes will come soon in an effort to standardize the file names
> between platforms, between releases, and between products (Mozilla vs.
> Netscape).

That would be excellent. Calling Windows full installer "installer"
whereas the Linux stub installer is the one called "installer" has
confused several people.

Gerv