Slashdot Mirror

← Back to Stories (view on slashdot.org)

Mozilla Milestone 14 Awaits

Posted by timothy on from the back-to-lucky-numbers dept.

Anderson Silva (among others) zapped us the news that you can now grab Mozilla's M14 release (Seamonkey). The Mozilla Organization's site doesn't yet reflect M14's availability, but it will soon. For now, here are the release notes. So grab, test, and gripe -- bug reports will only make the Mozilla browser better.

4 of 256 comments (clear)

  1. Use a talkback build by linuxci · · Score: 5
    If you're using Windows or Linux please consider downloading a talkback build (they have talkback in their filename) this'll automatically send back crash data (with your permission - a box will appear first) to the Mozilla team which will help them track down the main causes for Mozilla to crash.

    BTW the source code for M14 should follow on the FTP site soon. If you can buld for other platforms please do so and contribute your builds back to Mozilla. See here for details of packaging your own milestone build for your platform.
    --
    Make use of your spare CPU time!

  2. Don`t forget about Mozillazine! by Sits · · Score: 5

    Mozillazine is a website manned by helpful volunteers hoping to make Mozilla the best browser possible. If you are unsure as to how to get started bug testing, I recommend stopping by #mozillazine for a friendly chat.

  3. Bug Reports by asa · · Score: 5

    Mozilla releases these milestone checkpoints with the hopes that lots of people will take a look and give some feedback. Bug reports are the best way to give this feedback. Mozilla's bug database Bugzilla (located at http://bugzilla.mozilla.org ) provides some really nice tools for reporting bugs and feature requests. Before reporting any bugs it is a good idea to give the database a query to see if your bug has already been reported. This will save mozilla QA a lot of time weeding through duplicate bug reports. You can search the database at http://bugzilla.mozilla.org/query.cgi . Start off with simple searches in the Description field. If that yields too many bugs to weed through you might add more to the search. If you find your bug reported please add any relevant comments to that bug report. If you find that your bug is not reported then please take a quick glance at the bug reporting guidelines before making your report. These guidelines will help you report a bug that developers and QA can track down and fix more swiftly. The bug reporting guidelines ca be found at http://www.mozilla.org/quality/bug-writing-guideli nes.html . If you are new to the process you might try the new Bugzilla Helper which will guide you through the process. Remember that the better the report the more quickly it will get confirmed, assigned and fixed. Thanks, and enjoy M14 (for those that like to stay on the bleeding edge, M15 cycle nightly builds have been available for a few days now.)

    Asa
    external QA on the Mozilla project

  4. Re:This better not be M14 by Slothy · · Score: 5

    The problem here is that you're using an SMP box and Mozilla is not yet thread-safe, though I have NO idea why they don't put this is big bold letters on the M13/14 pages. So people with a single CPU have a fairly rock-solid browser, and people with SMP boxes think this should probably be Milestone 3.

    The bug for this is:

    http://bugzilla.mozilla.org/show_bug.cgi?id=2155 6