mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-01-14 22:13:31 +00:00
08c4128fcd
We now have a "source" task that produces JSON files with per-file Bugzilla components and a list of files missing a declared Bugzilla component. gzip variations are also produced. The files are published in the index so clients can query e.g. gecko.v2.mozilla-central.latest.source.source-bugzilla-info/public/components.json and get the latest metadata. This should help alleviate the need for querying the moz.build evaluation API on hg.mozilla.org - or at least facilitate bulk queries of the data from a static source. MozReview-Commit-ID: 9fAoPSt4bxq --HG-- extra : rebase_source : bad6912a5e2bf5f4791e97f0d0b2572d70007e9a
An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:
https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
For information on how to build Mozilla from the source code, see:
https://developer.mozilla.org/en/docs/Build_Documentation
To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
https://developer.mozilla.org/en/docs/Creating_a_patch
https://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree
If you have a question about developing Mozilla, and can't find the solution
on https://developer.mozilla.org, you can try asking your question in a
mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups
are accessible on Google Groups, or news.mozilla.org with a NNTP reader.]
You can download nightly development builds from the Mozilla FTP server.
Keep in mind that nightly builds, which are used by Mozilla developers for
testing, may be buggy. Firefox nightlies, for example, can be found at:
https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
- or -
https://nightly.mozilla.org/