Slashdot Mirror


Mozilla.org Releases Mozilla 1.0 Release Candidate

asa writes: "Today mozilla.org made available for download binaries of Mozilla 1.0 Release Candidate 1. RC1 will be used to gather feedback and crash data in preparation for an RC2 or a final release. Please hammer on these builds, report bugs and send in talkback reports. New to RC1 are fixes for about 2000 bugs including more than 150 crash fixes so grab a build and let us know what you think."

3 of 59 comments (clear)

  1. Some sweet add-on's for Mozilla by yota · · Score: 5, Informative
    Spellchecker: For who can't spell.

    Optimoz: add gestures to Mozilla.

    Enigmail: add PGP/GPG support in Mozilla Mail.

    Googlebar: the cool Googlebar for Mozilla too.

    And if you want more just look in MozDev and you'll find something interesting.

    Andrea

  2. Comment removed by account_deleted · · Score: 5, Informative

    Comment removed based on user account deletion

  3. Help wanted by Sits · · Score: 5, Insightful

    Quick plea - if you have filed an unconditional bug that hasn't seen activity for a month or two check whether it is still valid. If not resolve it worksforme. Thanks.

    With all this increased testing, more and more bugs are being filed at increasingly speedier rate and the Bugzilla database could always do with an extra hand to stop bug counts spiralling out of control.

    Plug
    Over in #kill-unco on irc.mozilla.org we are trying and reduce the number of unconfirmed bugs. The more help we get, the sooner people's complaints are serviced and the sooner they can be fixed.

    Sometimes unconditionals slip through intial net of bugzilla marshalls and just wind up being forgotten about. This can happen because the intial marshalls don't have access to the same platform or don't use a particular component much (macs, mail and news/java spring to mind). Other times the reporter doesn't file enough information and needs to be prompted for more. Often unconditionals are filed subsequently fixed by other bugs but not closed by their original reporters. All these things make for a messy database and engineers could use up
    time marking dups rather than fixing bugs.

    A few moments of your time could save engineers from going mad seeing the same bug reported by reported in 30 different places. If each slashdot reader helped resolve just two mozilla bugs a day then we could all get a better browser...