canmove, Confirmed users
345
edits
No edit summary |
No edit summary |
||
| Line 23: | Line 23: | ||
=== Fully-Tracked Changes === | === Fully-Tracked Changes === | ||
Even tiny changes must be fully documented in the bug-tracking | Even tiny changes must be fully documented in the bug-tracking system, with full justifications for the change and a specific patch posted directly to the bug report. This rule is enforced largely by necessity--a vast number of our contributors don't have access to our version-control system, and are located across the world from each other. Thus, they '''must''' file a bug and post a patch in order for us to even know about it. Contrast this to a commercial development environment where developers are ''supposed'' to post changes to the bug-tracking system, but don't necessarily always ''have'' to do so in order to actually get code checked in. | ||
system, with full justifications for the change and a specific patch | |||
posted directly to the bug report. This rule is enforced largely by | |||
necessity--a vast number of our contributors don't have access to our | |||
version-control system, and | |||
order for us to even know about it. Contrast this to a commercial | |||
development environment where developers are ''supposed'' to post changes | |||
to the bug-tracking system, but don't necessarily always ''have'' to do | |||
so in order to actually get code checked in. | |||
=== Code Review === | === Code Review === | ||
| Line 74: | Line 66: | ||
various different versions of Perl in various different configurations | various different versions of Perl in various different configurations | ||
to assure that the code is not broken and follows our quality | to assure that the code is not broken and follows our quality | ||
standards. Any failure of this test suite will warn the developers who | standards. Any failure of this test suite will warn the developers, who | ||
are forbidden to check any other code into version-control until the | are forbidden to check any other code into version-control until the | ||
problem is fixed. | problem is fixed. | ||
| Line 103: | Line 95: | ||
=== Testing on a Major Installation === | === Testing on a Major Installation === | ||
Usually before a major release, bugzilla.mozilla.org will | Usually before a major release, [https://bugzilla.mozilla.org bugzilla.mozilla.org] will upgrade to our latest development code. This is a Bugzilla installation with tens of thousands of active users, and over 400,000 bugs filed. | ||
upgrade to our latest development code. This is a Bugzilla installation | |||
with tens of thousands of active users, and over 400,000 bugs filed. | |||
=== QA === | === QA === | ||
| Line 116: | Line 106: | ||
and their results. | and their results. | ||
The QA manager is himself one of the primary developers of | The QA manager is himself one of the primary developers of Bugzilla. | ||
Bugzilla. | |||
Any serious bugs found by QA are fixed before the release, and | Any serious bugs found by QA are fixed before the release, and | ||