Follow Slashdot stories on Twitter

 


Forgot your password?
Close
typodupeerror
×
Mozilla The Internet

Mozilla.org Releases Mozilla 1.0 Release Candidate 59

Posted by timothy from the they're-askin'-for-it dept.
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."
This discussion has been archived. No new comments can be posted.

Mozilla.org Releases Mozilla 1.0 Release Candidate More

Mozilla.org Releases Mozilla 1.0 Release Candidate

Comments Filter:
  • Got it and have no compelling reason to switch back to IE except for Windows Updates. (Under Linux at home I am still going to use Galeon)
    • Is this me talking? I am the exact way...except backwards. I swear by Galeon at work (and would give my left everything for a Windows version...ha!).

      At home, my XP box has IE for Windows Update and that's it. In fact, I find now that Java runs much better under Mozilla, and only a few movie formats aren't better in Mozilla.
  • This release seems like a very stable release. I've been running it for many hours now (compiled from cvs) and it has been faster and generally more pleasant than MZ0.9.9. And I really like the new download manager =). Mail return recipts aren't bad either!
    • Can you drop the right cvs switches to get RC1? I have some patches [google.com] I need to apply before I can use mozilla. Gracias.


      • It's in the README

        http://ftp.mozilla.org/pub/mozilla/releases/mozi ll a1.0rc1/README
      • You could probably just get the source tarball and patch that!? If not, you need to checkout the MOZILLA_1_0_RC1_RELEASE cvs tag. Use the build configurator to make a .mozconfig file, and put in CVS tags, co: -P -r MOZILLA_1_0_RC1_RELEASE . That should do the trick.
  • All of us down here at the lab use Mozilla every day. We created a CGI app that lets us view the particles in the chamber in real time. We just point our browsers to http://particle.accelerator.net and we see the electrons, muons and gravitons in their orbits within the cyclotron.

    Anyway, Moz 0.9.9 had a bug where we could only see positively charged particles. But the good folks at mozilla.org fixed that right up for us. Now if only they'd patch it so we could see particles with no mass...

  • Mozilla Embed control? (Score:3, Interesting)

    by psavo ( 162634 ) <psavo@iki.fi> on Thursday April 18, 2002 @04:28PM (#3368770) Homepage
    Some time ago I read an article on newsforge that it's really easy to switch from IE to Mozilla when using it as a html viewing engine -> the calls are all exactly same.

    Now I'm thinking.. Is it possible to switch that in already build (binary) application? Like ditch that mshtml.dll or something like that?

  • Even Mozilla 0.9.9 is excellent. (Score:4, Insightful)

    by Futurepower(R) ( 558542 ) on Thursday April 18, 2002 @04:36PM (#3368820) Homepage

    I'm using Mozilla 0.9.9, and even that earlier version is excellent.

    Good work, Mozilla team.

    I know that some people will have trouble with a warm statement such as this, but here it is anyway:

    Mozilla is an act of love. There are many ways to be loving, and supplying a much-needed tool to the whole world is one of them.

  • View Source bug (Score:3, Informative)

    by wraithgar ( 317805 ) on Thursday April 18, 2002 @04:49PM (#3368907) Homepage Journal
    Yeah, the biggest reason everyone where I work is getting exited is because the View Source bug was finally fixed a week or so ago, and this is the first major release that will incorporate the code.

    Woohoo!!
  • the announcement that rc1 is near goes on the front page and the day it's released it slips into the developers section

    I got the 10meg Windows version in 5 minutes and that's across the atlantic (caches not withstanding)

    thanks /.

    I guess the FreeBSD port will be updated over the weekend, my cron will auto upgrade that one in the wee hours.

    I hope my favourite bug of not displaying the url in the address bar until you press refesh has gone
    • I know, I thought once mozilla-announce appeared in my mailbox, the server would already be /.'ed. But, I got the 7.x RPMs and the Windows build in a matter of seconds.

      Kinda nice.

  • It's had a major speedup (Score:3, Interesting)

    by DrSkwid ( 118965 ) on Thursday April 18, 2002 @04:57PM (#3368951) Journal
    I'm running RC1 with crash feedback and boy, someone gave it a turbo boost!

    well done thank you thank you thank you er AOL ;)

  • The Beast Shall Be Made Legion! (Score:1, Funny)

    by Anonymous Coward
    The prophecy [about] is coming to pass! Repent sinner, the end is nigh!

  • Some sweet add-on's for Mozilla (Score:5, Informative)

    by yota ( 165006 ) on Thursday April 18, 2002 @05:18PM (#3369095)
    Spellchecker [mozdev.org]: For who can't spell.

    Optimoz [mozdev.org]: add gestures to Mozilla.

    Enigmail [mozdev.org]: add PGP/GPG support in Mozilla Mail.

    Googlebar [mozdev.org]: the cool Googlebar for Mozilla too.

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

    Andrea

    • Don't install alpha products. Wait for them to mature. They make whole mozilla to crash constantly. Especially the google toolbar.

      • Re:Some sweet add-on's for Mozilla (Score:4, Insightful)

        by jbn-o ( 555068 ) <mail@digitalcitizen.info> on Thursday April 18, 2002 @10:43PM (#3370858) Homepage
        Don't install alpha products. Wait for them to mature. They make whole mozilla to crash constantly.

        Last time I looked, helping to find bugs was part of the communal development of Free Software. We should try stuff out, report bugs, and supply patches so we can all have better software. If we "[w]ait for them to mature" they'll mature far more slowly (if at all) and we'll be waiting longer.

        • Well, mozilla crashes randomly after installing some of these add-ons. Unfortunately I didn't find an easy way to uninstall them. When mozilla crashes, there is nothing indicating what crashed mozilla or what the bug is. In my case, I installed the google toolbar and mozilla started crashing constantly. How does that help anybody?
          • How does that help anybody?

            Perhaps one of the developers will chime in and help clear this up. I believe Talkback builds are put together to catch crashes and return valuable data back to the development team. A similar question could be asked of coredumps on Unix boxes—they help because they allow post-mortem analysis.

            • A talkback message will be generated and sent to a Mozilla developer. If this developer is half awake, he should forward the message on to the Google team for their use. The simple matter of getting the talkback messages should help both sides of the fence.

              As an addendium, sometimes the problem isn't the plug-in. It could be that the Google bar is using some new API call that no one else used. Best to install and let the developers make the decision.
            • If mozilla is aiming to become a software platform in the future, a simple plugin shouldn't be able to crash the whole platform.
      • Normally I like to experiment, but I just upgraded from 0.9.9 (with mozdev spellchecker working OK) to RC1, and somehow its still picking up the spellchecker (how, anyone?!) and locks up the machine EVERY time I try to send email!!

        So I've rolled back to 0.9.9 again, and although it recognizes the spellcheker, I still can't send email.

        F**k that!

        To be honest, leave the alpha add-on's until 1.0 and frozen API's - because in the meantime how are you supposed to know what is RC1's fault, or something to do with whatever random XPI you are running.

        If you want to help log bugs for projects - great!
        But right now we need to know what's wrong with the Moz RCs, and there's no easy way to tell that if you have X alpha extensions plugged in!

        Until there is a stable 1.0 of Moz with frozen APIs then debugging these alpha projects is a hopeless task, which I should think is why most of the projects at MozDev are stale at best!

        The best way to help MozDev projects is to ensure that Moz 1.0 is as bug free as possible - they they can have something stable to build against!
        • Just to follow up on my own experience here...

          I fixed my probs with new Mozilla installers picking up XPIs installed for old versions which are not compatible...

          For Windows slaves, uninstall Mozilla using the control panel, AND then go to Program Files/Mozilla.org and delete the whole Mozilla subdirectory.

          HOWEVER, you may want to be more selective with what's left. Probably you'll want to delete everything except Mozilla/Plugins.
      • Whoa, whoa, whoa. The Googlebar is making your system crash? As one of the developers behind it, I've kept an eye on the mailing list and user notes pages, as well as trying to test every release myself, and never had or heard of any problem of the sort. If you'd care to explain the problem as much as possible, we can try and fix it, or at least track down the real culprit. Yes, there are bugs, but...
  • There's still the (windows) bug in the classic theme, where when you minimize mozilla, it doesn't. Which sucks because I like classic.

  • Comment removed (Score:5, Informative)

    by account_deleted ( 4530225 ) on Thursday April 18, 2002 @05:36PM (#3369205)
    Comment removed based on user account deletion

  • Help wanted (Score:5, Insightful)

    by Sits ( 117492 ) on Thursday April 18, 2002 @05:37PM (#3369210) Homepage Journal
    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 [sucs.org] 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...

    • Re:Help wanted (Score:1, Informative)

      by Anonymous Coward
      UNCONfirmed, not UNCONditional, think about what the word means
  • RC1 has bookmark groups - this means that with one bookmark you can open a large amount of pages that'll start loading in various tabs.

    Also, as evidenced by bug 138000 (http://bugzilla.mozilla.org/show_bug.cgi?id=13800 0 - copy/paste yourself, no linking from slashdot allowed), we will almost certainly see a release candidate 2 before the final version of 1.0 will see the light. (Though I could imagine RC1 performing so well that they'll integrate RC2 with 1.0 final after all.)

  • Congrats to Mozilla team! (Score:3, Insightful)

    by molo ( 94384 ) on Thursday April 18, 2002 @06:00PM (#3369382) Journal
    Posted with:

    Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0rc1) Gecko/20020418

    Downloaded the i386 RH 7.x RPMs and rebuilt on RH 6.2. Works like a charm.

    Thanks, Moz team!
  • I'm hoping they fix 130614 [mozilla.org] soon. I've got a Win98SE box which I cleaned up using Revenge of Mozilla (thus making it much like win95), and this is keeping me from using recent versions of Mozilla on that box. Fortunately I don't use that box very often.

  • Not on Frontpage? (Score:2, Insightful)

    by tk422 ( 446096 )
    Why the heck isnt this on the frontpage? Mozilla *needs* testers especially right now and were stuck in the developer section??

    Especially since the articles saying Mozilla 1.0RC will be out soon was posted on the frontpage. Come on slashdot lets go!
    • Why the heck isnt this on the frontpage? Mozilla *needs* testers especially right now and were stuck in the developer section??

      Yup, I just submitted the news in the unlikely event that every /. reader missed it. I'm sure I'm not the only one. Maybe the /. team will act differently next time when they now have to sit and reject several hundred submissions...

  • Moz sure has shaped up since the early betas!

    I hope after 1.0 is realeased the developers will have time to finally address the completely unstable plugin interface on Linux (plugin barfs ==> Mozilla crashes).

    [not complaining, just anxious to have resolved what is IMHO a huge bug]
  • I've been using the nightlies since 0.9.9 and they've all been good and getting better.
  • The non-MacOS X version is now described as being for MacOS 9.x. I tried to run it on my 8.6 system and it hangs on launch. 0.9.9 was described as being for 8.x and 9.x, and it runs fine on 8.6 (I'm posting from it). I know, maybe I should upgrade my OS, but my company won't spring for any Mac upgrades, and I run a slower PowerMac at home - MacOS 9 is too slow for it. Rats. I've been looking forward to final on Mozilla and now I can't run it.

  • Have they even bothered to testing this version?

    I don't think so, the preference is broken, categories cannot be selected, so it's not possible to configure Mozilla. I cannot configure my proxy, so my testing has not gotten very far.

    So I pop over to the BugZilla site to report the bug, and I have to start jumping through hoops, why the need to pre-register to report bugs? What happened to the idea that many eyes make bugs shallow ?

    My advice wait for the next release candidate.

    • Well I am using latest cvs on Linux and its stable so far...

    • Don't install over an exisiting Moz directory, clear it out, then do the install.

      I've had the same issue on the RC1 nightlies on Windoze, there is a mention of it somewhere on the release notes... somewhere...

      But this release is really quite nice, I'd hate to see it not get used for something thats really pretty minor.

    • Re:Wait for next RC. (Score:1)

      by Anonymous Coward
      Bugzilla complies to the 'Burrow the Post button' rule, that's all.

      If one could file bugs without being registered, Bugzilla would soon be bogged down by thousands dupes, invalid, or unconfirmable 'bugs'.
      Or worse, support questions (something as seen in the php.net user comments, 'I can't get that to work, why ?').
      Developers would have to swim through this sea of garbage to find the bugs that really need attention.

      And frankly, the registration process takes very little time. A lot of places require you to register nowadays in order to avoid the Anonymous Coward phenomenon, Bugzilla is just one of them.

      michel v,
      who is so lazy he didn't check that he entered the right password
    • As one of the other comments suggested deleting your profile/mozilla directory an reinstalling may fix this. Take a look at http://bugzilla.mozilla.org/show_bug.cgi?id=137952 for further detail.
    • If that's the best you can do to explain the bugs you're seeing, then perhaps it's just as well that you haven't bothered to register for a bugzilla account.

      There are those who believe that with a little help from everyone, Mozilla will become the best browser on every platform. And there are those who believe that Mozilla "sucks" currently, or laziness sets in, so there's no reason to help out at all. For the first set, I invite you to check out http://www.mozilla.org/get-involved.html [mozilla.org]. With just a bit of your time, you can help make Mozilla the best browser on any platform. And every time you spend 15-30 minutes helping out the project in whatever way you choose to, keep in mind that someone else has spent 30 minutes helping fix something that won't be a problem for you. That's why it works.

      In the end, if something you come across isn't working, and you do nothing to help, then it's your fault. The project only gets better when you do the work to properly post your bugs to Bugzilla.

      - Adam

Slashdot Top Deals

A complex system that works is invariably found to have evolved from a simple system that works.

Close