Confirmed users
656
edits
Education/Courseware/MozillaForProfessors: Difference between revisions
Jump to navigation
Jump to search
Education/Courseware/MozillaForProfessors (view source)
Revision as of 18:11, 18 May 2009
, 18 May 2009→Collaboration
| Line 112: | Line 112: | ||
# Select the [https://bugzilla.mozilla.org/userprefs.cgi?tab=email Email Preferences] tab | # Select the [https://bugzilla.mozilla.org/userprefs.cgi?tab=email Email Preferences] tab | ||
# Scroll to the bottom under '''User Watching''' and add the bugmail address for the user you wish to watch | # Scroll to the bottom under '''User Watching''' and add the bugmail address for the user you wish to watch | ||
==='The Tree': Tinderbox, HG, Try Server, Talos=== | |||
Since so much of the work going on within Mozilla is focused on the development of various software products, and since development takes place in parallel by developers around the world, a lot of work goes into making sure the source code builds, hasn't regressed in terms of functionality or performance, etc. | |||
For the most part, these details are not interesting in the educational context (at least not at first), but some awareness of them will help you to understand some of what is going on within the project. | |||
First, the 'tree' is the code in revision control. Mozilla uses Mercurial (HG), a distributed revision control system. You can get (i.e., clone, see below) a local copy of the hg repositories to work against. You can also see the latest changes and versions of files by visiting Mozilla's [http;//hg.mozilla.org HG Web] interface. There are many repositories, but here are a few to focus on initially: | |||
* [http://hg.mozilla.org/mozilla-central/ mozilla-central]: Firefox | |||
* [http://hg.mozilla.org/comm-central/ comm-central]: Thunderbird, SeaMonkey | |||
* [http://hg.mozilla.org/mobile-browser/ mobile-browser]: Fennec Mobile Browser | |||
You can see the health of the tree at any given time by looking at [http://tinderbox.mozilla.org/showbuilds.cgi Tinderbox]. For example, to see the current status of Firefox, you look [http://tinderbox.mozilla.org/showbuilds.cgi?tree=Firefox here]. You only need to pay attention to the top row and the colours of each. When you get the source yourself, you'll want to make sure that it is '''green''' and will build. | |||
At the time of writing, the tree was '''CLOSED''' (meaning developers are not allowed to commit new work), the ''OS X 10.5.2 mozilla-central unit test'' machine was orange (meaning a unit test failed after building), ''WINNT 5.2 mozilla-central unit test %'' was "burning" (meaning the build had failed), and all other trees were green (build and/or tests succeeded). | |||
Developers can see graphs of various performance and other data for each build/test run using systems like [https://wiki.mozilla.org/Buildbot/Talos/Machines#Graph_Links Talos]. Developers with commit rights (i.e., who have been granted the right to check-in code), can also test their work against the [https://wiki.mozilla.org/Build:TryServer Try Server]. This allows them to see the effect of building and running tests on all 3 main platforms before actually checking in any code. | |||
Most of this can be ignored as you get started. But knowing what certain terms mean, and where to look for information as you get more comfortable, is important. | |||
=Mozilla Technology= | =Mozilla Technology= | ||