This bug is to track any needed changes before stub installer can be enabled on mozilla-central. Depending on scope of work, this bug (or maybe a separate bug?) would track the changes needed to support stub-installer in mozilla-aurora / mozilla-beta /mozilla-release / mozilla-esrNN Requirements still unclear, but here's what we know so far: 1) We know stub installer is win32 only at this time. Specifically, win64 is out of scope. Also out of scope is OSX and linux. 2) Per bug#322206, on win32, we will be be supporting *both* current all-in-one-installer *and* new stub-installer. 3) stub installer will use a hardcoded url to bouncer, e.g. to the "firefox-latest" product. For now, we're using a workaround of "firefox-latest" in bouncer. 3a) this will eventually be replaced by a bouncer change that WebDev are working on. See bug#398366 for details. Note that this WebDev change will only work for beta/release builds, and is not scoped to work with try/nightly/depend builds. 4) how will QA test the stub installer for a release before the complete installers are copied into the final location and product details / bouncer updated?

Who's on point for this? Given that e-mail says we're shipping on Monday we need an owner pronto.

I don't know how useful this bug is, but assigning to catlee because he's leading stub installer from our side.

I think we're done here for now.