Bugzilla:Developers: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 9: Line 9:
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.
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.


5. [[Bugzilla:Patches|Make a patch]]
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.


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


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


7. 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.
8. [[Bugzilla:Review|Ask for review]]


8. [[Bugzilla:Committing_Patches|Commit your patch]], or get somebody else to commit it for you.
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.
 
10. [[Bugzilla:Committing_Patches|Commit your patch]], or get somebody else to commit it for you.


== Articles and Policies ==
== Articles and Policies ==
canmove, Confirmed users
345

edits