You'll be amused to know that Mozilla 1.2.1 differs from Mozilla 1.2 by one character.
Ok, not exactly. It actually differs by 34 characters. The bug fix itself was a one character change (changed a '9' to an '8'). Changing the version string in various places from "1.2" to "1.2.1" took 33 characters.
Help us test the 1.0 branch by trying out that build and making sure no horrible regressions have crept in.
slashdotters, do your thing!
Re:What happens to Talkback bug reports?
on
Mozilla 0.9 Out
·
· Score: 5
>After for first two or three crashes, I stop
>sending them because I fear my duplicate
>Talkback bug reports are causing some Netscape
>employee to curse my name.. "damn! it's that
>same guy sending in a dozen bug reports for the
>same silly crash!":-)
Heh. Not quite. The crash reports go to a database, not to people. If Mozilla crashes for you during normal everyday use, then you should report each crash. The most common crashes are the ones that tend to get the most attention so if you neglect to report all your crashes, then you're just making them look less common. I'm not sure exactly how the data is tabulated but it can't hurt to report each crash.
On the other hand if you crash in the same place over and over to just spam talkback then yes, you'll be cursed at.
Re:Please use talkback builds.
on
Mozilla 0.9 Out
·
· Score: 1
The only place to get talkback builds is from mozilla.org (or a mirror). I'd be very surprised if Ximian used talkback unless they're repackaging our builds.
The Talkback server is owned by Netscape so only builds provided to mozilla.org by Netscape can do talkback. Netscape doesn't build RPM's (blizzard at redhat makes those), Red Carpet only works with RPMs (i think) so no, I don't anticipate you getting talkback through Ximian.
Please, please, please, use our talkback builds on
Windows,
Macintosh
and
Linux.
Using talkback builds gives us more crash data
so common crash bugs can be quickly identified and fixed. Yes, people really do look at this stuff.
This is an incredibly easy way to report bugs.
You don't need a bugzilla account, you don't need
to write coherent english sentences and for a change, filing DUPLICATES IS GOOD!
Here's a sample
crash analysis page. Watch out, this page is 2+ MB.
You'll be amused to know that Mozilla 1.2.1 differs from Mozilla 1.2 by one character.
Ok, not exactly. It actually differs by 34 characters. The bug fix itself was a one character change (changed a '9' to an '8'). Changing the version string in various places from "1.2" to "1.2.1" took 33 characters.
Help us test the our new ftp servers by
s t- 1.0.0// latest-1 . .0/
downloading the latest nightly branch build
from either of:
http://ftp.mozilla.org/pub/mozilla/nightly/late
ftp://ftp.mozilla.org/pub/mozilla/nightly
Help us test the 1.0 branch by trying out that build and making sure no horrible regressions have crept in.
slashdotters, do your thing!
>After for first two or three crashes, I stop :-)
>sending them because I fear my duplicate
>Talkback bug reports are causing some Netscape
>employee to curse my name.. "damn! it's that
>same guy sending in a dozen bug reports for the
>same silly crash!"
Heh. Not quite. The crash reports go to a database, not to people. If Mozilla crashes for you during normal everyday use, then you should report each crash. The most common crashes are the ones that tend to get the most attention so if you neglect to report all your crashes, then you're just making them look less common. I'm not sure exactly how the data is tabulated but it can't hurt to report each crash.
On the other hand if you crash in the same place over and over to just spam talkback then yes, you'll be cursed at.
The only place to get talkback builds is from mozilla.org (or a mirror). I'd be very surprised if Ximian used talkback unless they're repackaging our builds.
The Talkback server is owned by Netscape so only builds provided to mozilla.org by Netscape can do talkback. Netscape doesn't build RPM's (blizzard at redhat makes those), Red Carpet only works with RPMs (i think) so no, I don't anticipate you getting talkback through Ximian.
Here's a sample crash analysis page. Watch out, this page is 2+ MB.