5
edits
(don't forget SeaMonkey aka Mozilla 1.8) |
|||
| Line 21: | Line 21: | ||
== Will you be looking at feedback from old builds? E.g. will you be looking at crash data from Firefox 1.5 in a month? Or is it only crashes in recent builds that are interesting? == | == Will you be looking at feedback from old builds? E.g. will you be looking at crash data from Firefox 1.5 in a month? Or is it only crashes in recent builds that are interesting? == | ||
This is a great question and the answer will explain exactly why we need more help from the community. To get a better understanding of which builds need to be looked at, you first need to understand which development branches exist and which product releases come off of them: | This is a great question and the answer will explain exactly why we need more help from the community. To get a better understanding of which builds need to be looked at, you first need to understand which development branches exist and which product/project releases come off of them: | ||
* Mozilla Trunk ( | * Mozilla Trunk (FirefoxTrunk, ThunderbirdTrunk, MozillaTrunk [SeaMonkey]) | ||
* Mozilla 1.0 Aviary Branch ( | * Mozilla 1.7/1.0 Aviary Branch (Firefox10, Thunderbird10, Mozilla17) | ||
* Mozilla 1.8.0 Branch (Firefox15, Thunderbird15) | * Mozilla 1.8.0 Branch (Firefox15, Thunderbird15, SeaMonkey10) | ||
* Mozilla 1.8 Branch (Firefox2, Thunderbird2) | * Mozilla 1.8 Branch (Firefox2, Thunderbird2, SeaMonkey11) | ||
Looking at that list, I'll try to explain what type of crash analysis needs to be done for each: | Looking at that list, I'll try to explain what type of crash analysis needs to be done for each: | ||
edits