Closed
Bug 1372944
Opened 7 years ago
Closed 5 years ago
latest-mozilla-beta-l10n/ be Firefox Developer Edition instead of Beta now
Categories
(Release Engineering :: General, defect)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: yfdyh000, Unassigned)
Details
STR: e.g. https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-beta-l10n/firefox-55.0.zh-CN.win32.installer.exe Actual results: The installer icon is a new icon and equal to https://archive.mozilla.org/pub/firefox/releases/55.0b1/win32/zh-CN/Firefox%20Setup%2055.0b1.exe, but the installer is Firefox Developer Edition.
Updated•7 years ago
|
Component: Operations: Product Delivery → General Automation
Flags: needinfo?(rail)
Product: Cloud Services → Release Engineering
QA Contact: oremj → catlee
Comment 2•7 years ago
|
||
Yes, this is us.
Comment 3•7 years ago
|
||
I wonder if we should stop publishing there completely...
Comment 4•7 years ago
|
||
Callek, do you know what publishes there? There are https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-release-l10n/ https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-beta-l10n/, but not https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-release/ nor https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-beta/. Sounds like we should tweak the l10n repack script so it doesn't publish to "latest". Maybe make https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/single_locale/production.py#10 per branch?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(bugspam.Callek)
Comment 5•7 years ago
|
||
(In reply to Rail Aliiev [:rail] ⌚️ET from comment #4) > Callek, do you know what publishes there? There are > https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-release-l10n/ > https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-beta-l10n/, > but not > https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-release/ nor > https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-beta/. Sounds > like we should tweak the l10n repack script so it doesn't publish to > "latest". Maybe make > https://dxr.mozilla.org/mozilla-central/source/testing/mozharness/configs/ > single_locale/production.py#10 per branch? ...I'm not sure offhand, maybe make `stage_product` appropriate for devedition l10n?
Flags: needinfo?(bugspam.Callek)
Comment 6•6 years ago
|
||
I don't think beta/release builds should be publishing to the "latest" directories. It looks like we stopped doing that in the 59 beta cycle.
Assignee | ||
Updated•6 years ago
|
Component: General Automation → General
Comment 7•5 years ago
|
||
We haven't seen entries such as these for a good while now, I think we're good to close this bug.
Feel free to re-open if I'm wrong.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•