Bugzilla:Developers: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 7: Line 7:
3. If a bug has already been filed for what you want to do, check its [[Bugzilla:Priority_System|priority]].
3. If a bug has already been filed for what you want to do, check its [[Bugzilla:Priority_System|priority]].


4. Write some code. Make sure that you follow the [http://www.bugzilla.org/docs/developer.html Developer's Guide]. If you're new, you don't have to read the whole thing. Just read the [http://www.bugzilla.org/docs/developer.html#general General Guidelines], the [http://www.bugzilla.org/docs/developer.html#perl-style Style] section, and any other part that you think applies to the code that you're writing. Make sure that your patch is [[Bugzilla:Simple_Patches|as simple and small as possible]].
4. Check out the latest Bugzilla code from CVS. You can see instructions for how to do this on the [http://www.bugzilla.org/download/#cvs Bugzilla download page]. You always want to work against the latest CVS code of Bugzilla, not a released version, if you're writing patches that you want us to accept.


5. Test your patch. Make sure it works, and run ./runtests.pl in the Bugzilla directory. Also use [http://validator.w3.org the HTML validator] to make sure your code generates valid HTML, if you modified any of Bugzilla's HTML.
5. Write some code. Make sure that you follow the [http://www.bugzilla.org/docs/developer.html Developer's Guide]. If you're new, you don't have to read the whole thing. Just read the [http://www.bugzilla.org/docs/developer.html#general General Guidelines], the [http://www.bugzilla.org/docs/developer.html#perl-style Style] section, and any other part that you think applies to the code that you're writing. Make sure that your patch is [[Bugzilla:Simple_Patches|as simple and small as possible]].


6. [[Bugzilla:Patches|Make a patch]]
6. Test your patch. Make sure it works, and run ./runtests.pl in the Bugzilla directory. Also use [http://validator.w3.org the HTML validator] to make sure your code generates valid HTML, if you modified any of Bugzilla's HTML.


7. [[Bugzilla:Submitting_Patches|Submit your patch in Bugzilla]]
7. [[Bugzilla:Patches|Make a patch]]


8. [[Bugzilla:Review|Ask for review]]
8. [[Bugzilla:Submitting_Patches|Submit your patch in Bugzilla]]


9. Once your bug has passed review, the reviewer will ask for "approval". When approval is granted, you or the reviewer can commit the patch to CVS.
9. [[Bugzilla:Review|Ask for review]]


10. [[Bugzilla:Committing_Patches|Commit your patch]], or get somebody else to commit it for you.
10. Once your bug has passed review, the reviewer will ask for "approval". When approval is granted, you or the reviewer can commit the patch to CVS.
 
11. [[Bugzilla:Committing_Patches|Commit your patch]], or get somebody else to commit it for you.


== Articles and Policies ==
== Articles and Policies ==
Line 26: Line 28:


* [[Bugzilla:UI_Design]]
* [[Bugzilla:UI_Design]]
* [[Bugzilla:Simple_Patches]]


[[category:Bugzilla|D]]
[[category:Bugzilla|D]]
canmove, Confirmed users
345

edits

Navigation menu