Slashdot Mirror


Firefox 1.1 Scrapped

An Anonymous Reader writes: "The Firefox team has decided to scrap the planned 1.1 release (already in Alpha 2) and instead release the final version as 1.5 due to the significant number of bug fixes and changes. The 1.5 feature complete beta is expected next month." From the article: "We are planning for a Firefox 2.0 and 3.0, but will divide the planned work over (at this point) three major Milestones, 1.5 (September 2005), 2.0 (unscheduled) and 3.0 (unscheduled). All major development work will be done on the Mozilla trunk, and these releases will coincide with Gecko version revs."

8 of 482 comments (clear)

  1. So shouldn't the headline be by Anonymous Coward · · Score: 4, Informative

    "Firefox 1.1 renamed"?

  2. Re:They really need to fix autoupdate by recoiledsnake · · Score: 5, Informative

    If you read the comments yesterday you would have found that mozilla does staggered updates to ease the pressure on their servers and hence the auto update feature will be working in a day or two.

    --
    This space for rent.
  3. Re:They really need to fix autoupdate by linuxci · · Score: 5, Informative

    One of the main advantages of 1.5 is the improved update system. Everyone knows that the 1.0 one was not up to scratch that's why they spent a lot of effort improving it. Based on current nightlies I'd say they've done a good job.

  4. Re:Can you read this? by generic-man · · Score: 4, Informative

    Just get Opera. For years (as in, since their Windows 3.1 days) they've supported a zoom feature that enlarges text, graphics, and even Flash animations. They also support CSS-based modifications that, with one or two mouse clicks, render a site easily readable by anyone with bad eyes, no tolerance for Comic Sans, and/or people who disagree with the decision to render a page in 7-point grey-on-white text.

    Firefox and its army of extension developers will eventually re-implement Opera, but in the meantime the real thing is much better.

    --
    For more information, click here.
  5. Re:Can you read this? by linuxci · · Score: 4, Informative

    They do have a preference where you can set the minimum font size which would make things easy to read for you while not zooming text that's already big enough to read.

    Look in prefereces/options for fonts and there's a pref to set the minimum font size. It's not like it's a hidden pref or anything it's in the standard dialog

  6. Re:Does this mean they'll fix launch.yahoo.com bug by kbrosnan · · Score: 4, Informative

    I gave you a full answer yesterday.
    http://slashdot.org/comments.pl?sid=156428&cid=131 16785

    Not to mention you posted the same comment
    http://slashdot.org/comments.pl?sid=156428&cid=131 14118

    --
    These people look deep within my soul and assign me a number based upon the order I joined. -Homer Simpson
  7. Re:Slashdot should be more positive by smokestacklightning · · Score: 3, Informative

    Please - take the gloves off just because it's an OSS project. My personal experiences with the fox have been rapidly going downhill. I have it running on three machines right now, it's eating up 56MB, 98MB and 100+MB of system memory on each of the machines. I was hoping that they would have the resource leaks fixed in the upcoming release, but if I have to wait much longer - I am jumping ship.

    The lack of progress made since 1.0 is really dissapointing. It seems like they put everything they had into getting that release out (apparently a little hastily as my frequent crap-outs attest to) and they don't have much left.

    Oh - and don't give me that song and dance about how it's some rogue plugin causing all my headaches - two are fresh installs and the one topping out at 100MB is stripped down to just the Google toolbar plugin.

    Maybe the delay will give them time to get this release right ...

  8. Re:Version-Number Junkies? by BillyBlaze · · Score: 3, Informative

    As I understand it, it's not at all a political move, it's certainly not just to have a higher number. As I understand it, the way Firefox development works is, there's the CVS HEAD, which I guess you could consider similar to the 2.5 kernel series back in the day - unstable and quickly changing. Every so often, they make a branch off the head that will become a stable release. These releases are kind of dead ends, but that allows them to be more stable and have more static APIs. So what this article actually means is, a while after the 1.0 fork, they started the 1.1 fork, but now they've decided that even the 1.1 fork is too far behind the head, and so they've opted to focus their stabilization efforts on the 1.5 fork, which already includes bugfixes that would otherwise have to be backported.