Open
Bug 1374008
Opened 9 years ago
Updated 9 years ago
Documentation about the build process of the developer edition is missing
Categories
(www.mozilla.org :: Pages & Content, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: shalokshalom, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170617224104
Steps to reproduce:
https://www.mozilla.org/de/firefox/developer/
Actual results:
Where is the source code?
IRC was the only source to find it
Then, no explanation, that this is actually the very same code from beta channel, simply the same package uploaded on two different places.
Zero information about the fact, that this is all about configure triggers and zero documentation about them specifically.
Expected results:
Point the source code obviously on the homepage
Mention that this is the beta code and developer edition results from build triggers
Document these triggers in the download file and elsewhere.
Updated•9 years ago
|
Component: Untriaged → Pages & Content
Product: Firefox → www.mozilla.org
Version: 55 Branch → Production
Comment 1•9 years ago
|
||
www.mozilla.org is a consumer orientated site. It's there to tell users about our products, their features, why they should use Firefox, and to provide a path to download the products. This page for Developer Edition is not really aimed at people wishing to learn how to build Firefox, and I don't it should really contain information that means very little to the vast majority of users reading it.
At the very least, I do however think we should include a link for where to find the source code, and to learn more.
Perhaps a link to this page? https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Source_Code
I'm not sure what would be more suitable as an alternative.
Comment 2•9 years ago
|
||
* and I don't think it should really contain information
| Reporter | ||
Comment 3•9 years ago
|
||
The thing is, that the link downloads a source code. At least on the Linux side. By the way: It looks awesome now.
You need to log in
before you can comment on or make changes to this bug.
Description
•