667
edits
Changes
no edit summary
** State your 0.1 release target on your project's wiki page (explain what you will have completed by the time you reach 0.1 release). Discuss this with your professor.
** Review, and where appropriate, comment on blog postings by other students.
== Week 5 (Sept 29) – Bugs, Bugzilla, and Debugging ==
* What is a bug?
** Open vs. Closed Bug Tracking - [http://www.arcanology.com/2007/09/19/ie-and-the-demise-of-borgzilla/ discussion of Mozilla vs Microsoft/IE]
** BMO - https://bugzilla.mozilla.org
** Searching for Bugs
** How to File a Bug
** Dupes, Depends, Blocks
** Following bugs through bugzilla
* Debugging Tools and Techniques
** C++ with VS.NET and gdb
** JS with Venkman and Firebug
** DOMi
** Error Console
** Lab - [[Dive into Mozilla Debugging Mozilla Lab|Debugging Mozilla]]
* '''Readings/Resources'''
** [[The Life-cycle of a Bug]] (on-line lecture) by Mozilla's Mike Connor
** [http://sparc.senecacollege.ca/pub/mozilla.lecture/mozilla-20073/vlad-debugging-seneca.avi Strategies for Debugging Mozilla] (on-line lecture) by Mozilla's Vladimir Vukićević
** [http://www.toolness.com/wp/?p=25 Account of fixing a first bug, by Mozilla's Atul Varma]
* '''TODO'''
** Create a [https://bugzilla.mozilla.org bugzilla] account
** Find 3+ bugs related to your project, and add them to your project wiki page
** CC yourself on two bugs that relate to your project
** Watch a user in bugzilla for the week and blog about the experience (e.g., ted, mfinkle, bsmedberg, or someone else related to your project)
** Be working on your 0.1 release. Ask for help if you're stuck
** Register for [http://fsoss.ca FSOSS] or join as a [[Volunteer|volunteer]].
** Come up with some ways for others to contribute to your project and add them to your project wiki page. Remember, you're asking for help, so be clear about what you need done, and make it easy so that people will pick you vs. another project.
