For the 2.0.5 security update and the 2.1a1 milestone, new versions will be needed to appear on crash-stats.
2.0.5 and 2.1a2pre both showed up in the admin console, so I created them. No crash reports show up yet with 2.0.6pre or 2.1a1 versions.
2.0.6pre has its first few reports and now has been added, so only 2.1a1 is still missing as still no crashes have been recorded there yet.
OK, finally, I could add 2.1a1 now as well.
Status: ASSIGNED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1a1
You need to log in before you can comment on or make changes to this bug.