Workflow description

The development process looks roughly like the process on Mozilla.org and aims at creating high-quality code and facilitating learning from other coders.

  1. Make sure to always use the latest code and documentation from GIT.
  2. Look in the bug tracker if your specific bug or feature request already has been reported. If this is not the case, enter a new bug report/feature request.
  3. Set yourself as the bug’s assignee to show you’d like to work on this bug. At this point, the bug status still is NEW.
  4. Assign the bug yourself when you’ve actually started to work on this bug. This will change the bug’s status to ASSIGNED.
  5. Use a test-first approach: When you add a new function or change a function, first write some unit tests that fail as long as the bug is not fixed and that pass when the bug is fixed.
  6. Write the necessary code and test it locally (in addition to the unit tests). Make sure it works and doesn’t generate any warnings or errors.
  7. Create a change set and push it to Gerrit..
  8. The reviewer might give you a - 1 and list the things that need to be changed. In that case, go back to the previous step and create a new patch.
  9. Or the reviewer might grant you the review, giving you a review+ (possibly listing some things that need to be changed bug that don’t require a new review).
  10. Resolve the bug report as FIXED.