Difference between revisions of "The Life-cycle of a Bug"

Revision as of 20:29, 30 September 2007

Time	Topic
1:18	Introduction of himself
1:45	What is a bug?
3:55	Bugzilla how bugs are described
4:30	How to read a a bug in bugzilla
5:28	How to deal with bugs in bugzilla
8:15	Understanding bug numbers
9:17	Firefox "won't fix" idea
14:07	Prioritizing features, functionality and bugs
18:28	blocker triage, workaround for bugs when released software is shipped
22:57	When switching browser version causing bugs
24:25	CVS patch
25:30	Patches waiting for review
26:22	Process of looking into a patch
28:50	What point should a bug should be stopped fixing?
33:33	When and how to rewrite the code
36:15	Issues with rewriting code
37:00	working in the open is different from close source view
42:15	Open Source community contribution
47:55	Writing patches which fixes the issue

Time	Topic
0:00	Major challenges facing by bug patching
3:23	Second review of patches
8:22	How does the Mozilla licenses related in the Rsesponsibilities of submitting a patch
10:37	Are all patches reviewed?
14:33	Automation to triage
16:16	Last step of the life cycle: QA
23:25	Ice Weezel
28:16	Saying "No" to bug fixes
33:23	Question from Dave Hamp-Gonzalves
38:17	Tricks on finding a good first good

@@ Line 46: / Line 46: @@
 <tr><td>8:22</td><td>How does the Mozilla licenses related in the Rsesponsibilities of submitting a patch</td></tr>
 <tr><td>10:37</td><td>Are all patches reviewed?</td></tr>
-<tr><td>14:33</td><td>Automation to treeosh</td></tr>
+<tr><td>14:33</td><td>Automation to triage</td></tr>
 <tr><td>16:16</td><td>Last step of the life cycle: QA</td></tr>
 <tr><td>23:25</td><td>Ice Weezel</td></tr>