Unify aurora and nightly bouncer entries

RESOLVED FIXED

Status

Release Engineering
Releases
RESOLVED FIXED
a year ago
a year ago

People

(Reporter: rail, Assigned: rail)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

It would be great to unify nightly and aurora bouncer entries. Currently we have the following entries:

 firefox-nightly-latest

 firefox-aurora-latest
 firefox-aurora-latest-l10n
 firefox-aurora-latest-ssl
 firefox-aurora-stub

We should at least add:

 firefox-nightly-latest-l10n
 firefox-nightly-latest-ssl
 firefox-nightly-stub

and probably 

 firefox-nightly-latest-l10n-ssl
 firefox-aurora-latest-l10n-ssl
In my testing firefox-aurora-latest-l10n already gives the "ssl" URL. Having the "-ssl" on the end is great with me though as it would be more consistent and should therefore lead to simpler code in bedrock and consistency is always nice.
Done for

    firefox-nightly-latest
    firefox-nightly-latest-ssl
    firefox-nightly-latest-l10n
    firefox-nightly-latest-l10n-ssl
    firefox-nightly-stub

https://wiki.mozilla.org/index.php?title=ReleaseEngineering%2FMerge_Duty%2FSteps&diff=1157250&oldid=1149341


Done for
    firefox-aurora-latest
    firefox-aurora-latest-ssl
    firefox-aurora-latest-l10n
    firefox-aurora-latest-l10n-ssl
    firefox-aurora-stub

https://wiki.mozilla.org/index.php?title=ReleaseEngineering%2FHow_To%2FEnable_or_Disable_Updates_on_Aurora&diff=1157251&oldid=1148199

BTW, I'm not sure if the "stub" link is used anywhere, but it is en-US only. I can add "firefox-nightly-stub-l10n" and "firefox-aurora-stub-l10n" if needed.
The "stub" products are used on mozilla.org, but not for nightly yet. firefox-aurora-stub is used, but changes to firefox-aurora-latest-l10n for non-en-US. Having firefox-(aurora|nightly)-stub-l10n would be helpful as long as we're sure that we do indeed have stub downloads available for all of the languages.
See the source for https://www.mozilla.org/de/firefox/channel/desktop/ for all of the download.m.o links generated for the various builds and platforms (CSS controls which platform's button is shown). Compare that with the en-US version for what we're currently doing differently for non-en-US: https://www.mozilla.org/en-US/firefox/channel/desktop/
Added 

  firefox-aurora-stub-l10n
  firefox-nightly-stub-l10n

https://wiki.mozilla.org/index.php?title=ReleaseEngineering%2FMerge_Duty%2FSteps&diff=1157398&oldid=1157250

https://wiki.mozilla.org/index.php?title=ReleaseEngineering%2FHow_To%2FEnable_or_Disable_Updates_on_Aurora&diff=1157397&oldid=1157251


Note that the stub installer is "win" only. There is no special version for win64, it supports both 32-bint and 64-bit.
I think we are done here. Let me know if we need to add/modify something.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → FIXED
(In reply to Rail Aliiev [:rail] ⌚️ET from comment #5)
> Note that the stub installer is "win" only. There is no special version for
> win64, it supports both 32-bint and 64-bit.

When you say "win" only, does that mean that if we were to request any of the "stub" products with the "win64" platform that it would 404, or it would send the same stub installer? Looks like right now we have a mish-mash on the site of when we use the "stub" and "latest" product names. So, when a stub is available, should we only have a "win" platform, and remove the "win64" unless we're offering full builds?
Just tested with curl and it looks like requesting a "stub" with the "win64" platform is indeed a 404. So the question remains whether we should only offer the stub or whether win64 people should just get the full build?
(In reply to Paul [:pmac] McLanahan from comment #8)
> Just tested with curl and it looks like requesting a "stub" with the "win64"
> platform is indeed a 404. 

Yup, it's "win" only, nothing for "win64". win64 support has been just added recently (bug 797208) and it'll take some time until it gets to release/ESR. But we have no plans to change release automation (see bug 1307956) and only win (32-bit) builds will get those compiled/published.

> So the question remains whether we should only offer the stub or whether win64 people should just get the full build?

Full build for now.
You need to log in before you can comment on or make changes to this bug.