667
edits
Changes
→Instructions
# File a '''dummy bug''' using Mozilla's [http://landfill.mozilla.org/bugzilla-3.0-branch/ test bugzilla]. NOTE: use '''Unclassified''' and '''dump unwanted bugs here'''.
# Do a '''debug''' build of '''Thunderbird'''. NOTE: you can obtain a build from your professor if something goes wrong.
# Confirm the existence of this bug. TIP: try creating a message with the text above, saving it to '''Drafts''', then open in '''Drafts''' to see how it gets rendered.
# Fix the bug. If you need a hint to figure out where to begin working, look [[Thunderbird Bug Fix Lab Hint|here]].
# Create a patch
# Test your patch [http://beaufour.dk/jst-review/ here] for common errors
# Attach your patch to the dummy bug you filed in step 1
# Get your patch reviewed by a classmate or your professor
== List of Valid/Invalid Email Address ==
Here is a list of some valid and invalid email addresses for testing: ===Valid Addresses===
* a@a.com
* a.a@a.a
* a.a@a.a.com
===Invalid Addresses===
* a@.
* a@..
== Resources ==
* [http://developer.mozilla.org/en/docs/Creating_a_patch Creating a patch for Mozilla]
* Build your own tree, or use this lab-friendly CVS Thunderbird tree:** Win32 http[https://cdot.senecac.on.ca/tb-cvsdeveloper.tgz 394M (NOTE: this must be extracted to C:\temp such that client.mk ends-up in C:\temp\tb\mozilla\client.mk)* Regular expression tester: http:org/en/zenit.senecac.on.ca/~chris.tyler/regexp/Simple_Thunderbird_build Thunderbird build documentation]
