Closed
Bug 1276106
Opened 9 years ago
Closed 3 years ago
Create stable system requirements URLs for Beta and Aurora
Categories
(www.mozilla.org :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: lmandel, Unassigned)
Details
For release system requirements we have the following URL:
https://www.mozilla.org/firefox/system-requirements/
We're going to use this in the stub installer as a reference for additional information when Firefox can't be installed due to not meeting the system requirements. We have the information in the stub to direct Beta and Aurora (and Nightly) installation attempts to system requirements pages specific for these branches. And, system requirements pages do exist for Beta and Aurora. Can we setup stable URLs like the above so that the stub doesn't have to create the URL itself?
The following will work although I'm not tied to the URL structure:
https://www.mozilla.org/firefox/beta/system-requirements/
https://www.mozilla.org/firefox/aurora/system-requirements/
Why isn't Nightly included? Only because we don't currently publish system requirements for Nightly.
Comment 1•9 years ago
|
||
Should this go to the website component? https://bugzilla.mozilla.org/enter_bug.cgi?product=www.mozilla.org
Updated•3 years ago
|
Product: Release Engineering → www.mozilla.org
Version: unspecified → Production
Comment 2•3 years ago
|
||
Is this still something we want? Looks like this request is nearly 6 years old. If so I do have a question.
So the idea is that these URLs would be redirectors to the newest system requirements of the latest release for that channel? e.g.:
https://www.mozilla.org/firefox/beta/system-requirements/
HTTP 302 ->
https://www.mozilla.org/en-US/firefox/97.0beta/system-requirements/
Also the Aurora channel no longer exists, so this would just be for beta?
Comment 3•3 years ago
|
||
Oh, and this already works. So I guess we can close this out?
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•