Installer filename(s) should include target OS and locale
Categories
(Firefox :: Installer, enhancement)
Tracking
()
People
(Reporter: Spampot, Unassigned)
Details
(Whiteboard: pm-triaged)
When you download Firefox or Thunderbird from the "official" download sites ...
https://www.mozilla.org/en-US/firefox/all/#product-desktop-release
https://www.thunderbird.net/en-US/thunderbird/all/
... then the installer filename will only contain the software version, but neither the target system nor the locale. On Windows the filename will always be
Firefox Setup <Version>.exe,
Thunderbird Setup <Version>.exe,
regardless if its for Win32, Win64, or ARM64, and regardless of which language you selected. This is inconvenient if you (like me) regularly download multiple installers at once like both 32/64-bit and both English and German. I'd therefore suggest to name the installers like
Firefox Setup 109.0 Win64 en-US.exe,
Thunderbird Setup 102.6.1 Win32 de-DE.exe,
and so on. Not a big deal, but would make things easier. What do you think?
|
||
Comment 1•3 years ago
|
||
Thank you for submitting this enhancement. Setting the component and waiting for the developer's opinion about it.
If this is not the correct component, please feel free to change it to a more appropriate one.
Hi!
Thank you for the feedback, the use case makes sense to me.
Carolyn, Nicole, I'm marking this as pm-triaged for your future consideration.
|
||
Comment 3•3 years ago
|
||
Functionally, I think this would end up in the releng organization. I'm not sure what would go into this change beyond renaming the artifacts -- updates to Bedrock, the stub attribution service, CDNs, etc. Absent additional compelling reasons to do this, the cost would not justify the benefit (IMO).
Ben, could you dupe to an existing ticket or change the component to releng if appropriate? Thanks!
|
||
Comment 4•3 years ago
|
||
I don't recall this ever coming up in the past (and a quick search of RelEng bugs doesn't turn anything up). The names are the way we are because of long standing desire to make them "pretty" (as opposed to the filenames we use on Nightly: eg: firefox-111.0a1.en-US.win64.installer.exe).
I agree that we ought not to consider this without a very strong upside. There's at least 15 years worth of things that depend on the current layout, and while many of them route through Bouncer (which deals with mapping things like https://download.mozilla.org/?os=win&lang=de&product=firefox-106.0 to paths on archive.mozilla.org), it's bound to be a far from trivial project that will bust both internal and external systems & automation.
Description
•