210
edits
Education/ComputerScience: Difference between revisions
→Release engineering
Jamesboston (talk | contribs) No edit summary |
Jamesboston (talk | contribs) |
||
| Line 21: | Line 21: | ||
Parts of Mozilla code can be separated from the platform and used inside your own applications. For instance, the Gecko rendering engine. For embedding basics and instructions visit the [https://developer.mozilla.org/en/Embedding_Mozilla Embedding] page at MDC. | Parts of Mozilla code can be separated from the platform and used inside your own applications. For instance, the Gecko rendering engine. For embedding basics and instructions visit the [https://developer.mozilla.org/en/Embedding_Mozilla Embedding] page at MDC. | ||
==Release engineering== | ==Build and Release engineering== | ||
<!-- | <!-- | ||
==[[Education/ComputerScience/ReleaseEngineering|Release engineering]]== | ==[[Education/ComputerScience/ReleaseEngineering|Release engineering]]== | ||
--> | --> | ||
A big part of getting a product like Firefox to market is the infrastructure for building and | A big part of getting a product like Firefox to market is the infrastructure for building and releasing the code. Unfortunately, there isn't much documentation at [http://developer.mozilla.org MDC] describing the process, but changing that is a goal of Mozilla Education. | ||
==[[Education/ComputerScience/Tools|Tools used by Mozilla]]== | ==[[Education/ComputerScience/Tools|Tools used by Mozilla]]== | ||