Difference between revisions of "The Life-cycle of a Bug"
Chris Tyler (talk | contribs) (→Media) |
|||
| (3 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
* '''Date''': Oct 11, 2006 | * '''Date''': Oct 11, 2006 | ||
| − | * '''Speaker''': Mike Connor | + | * '''Speaker''': Mike Connor, Mozilla Corporation |
| + | * '''License''': [http://creativecommons.org/licenses/by-sa/2.5/ CC-BY-SA] | ||
== Media == | == Media == | ||
| − | * [http://ilearn.senecac.on.ca/mozillalectures/lecture4part1.html Part I] (streaming) | + | * [http://ilearn.senecac.on.ca/mozillalectures/lecture4part1.html Part I] (streaming) - [http://video.google.com/videoplay?docid=4631757882037937249] (Google video) |
| − | * [http://ilearn.senecac.on.ca/mozillalectures/lecture4part2.html Part II] (streaming) | + | * [http://ilearn.senecac.on.ca/mozillalectures/lecture4part2.html Part II] (streaming) - [http://video.google.com/videoplay?docid=4539685494837402986] (Google video) |
* [http://ilearn.senecac.on.ca/mozillalectures/mozillalecture4.mp3 MP3] (93 MB) | * [http://ilearn.senecac.on.ca/mozillalectures/mozillalecture4.mp3 MP3] (93 MB) | ||
| Line 45: | 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>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>10:37</td><td>Are all patches reviewed?</td></tr> | ||
| − | <tr><td>14:33</td><td>Automation to | + | <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>16:16</td><td>Last step of the life cycle: QA</td></tr> | ||
<tr><td>23:25</td><td>Ice Weezel</td></tr> | <tr><td>23:25</td><td>Ice Weezel</td></tr> | ||
Latest revision as of 12:07, 5 February 2008
Talk Details
- Date: Oct 11, 2006
- Speaker: Mike Connor, Mozilla Corporation
- License: CC-BY-SA
Media
Talk Outline
Part I
| 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 |
Part II
| 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 |
