Slashdot Mirror


Mozilla Pitches Firefox 3.1 Alpha For July Release

An anonymous reader writes "Just a week after Mozilla shipped Firefox 3.0, the open-source developer has proposed ship dates for the next version that, if approved, would produce an alpha release next month and a final no later than early 2009. According to a draft schedule discussed at a recent meeting, Mozilla wants to have the first Firefox 3.1 developer preview ready by July, then move to a beta by August. The schedule slates final code delivery in the last quarter of this year or the first quarter of 2009. A month ago, when Mozilla first started discussing Firefox 3.1 internally, Mike Schroepfer, the company's vice president of engineering, said the upgrade's target ship date was the end of 2008. If Mozilla holds to that plan, Firefox 3.1 would be its first fast-track update. Firefox 3.0, for instance, launched approximately 20 months after its predecessor, Firefox 2.0."

60 of 257 comments (clear)

  1. No Offence To The Devs or Firefox by Vectronic · · Score: 5, Insightful

    But so what?

    There's nothing in the article or summary that hasn't already been covered in the other 76 articles about Firefox in the last 2 months.

    Firefox team is still developing Firefox... shit, so is Opera, so is IE, Safari, etc, etc...

    1. Re:No Offence To The Devs or Firefox by Kinky+Bass+Junk · · Score: 4, Insightful

      Err, release dates, maybe?

      --
      Anonymous Coward
    2. Re:No Offence To The Devs or Firefox by dnwq · · Score: 5, Funny

      It's developing faster.

      What significance that has depends on how much you care, I guess.

    3. Re:No Offence To The Devs or Firefox by dotancohen · · Score: 3, Informative

      Err, release dates, maybe?

      Release dates, what's that? Firefox2 didn't even make it to 2.1 after a year and a half, and Firefox1 jumped right up to 1.5.

      What is with Mozilla and their versioning?

      --
      It is dangerous to be right when the government is wrong.
    4. Re:No Offence To The Devs or Firefox by neokushan · · Score: 2, Insightful

      What's versioning got to do with release dates?
      It even says in the summary that this is to be the first "fast-track" update, hence the relatively minor version jump.
      Firefox 3 was a huge leap over firefox 2, hence the major jump. 1.5 was more of an extension to FF1 than an entirely new version, so to me, at least, the inconsistent version numbers are consistent with the changes and additions to the browser.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    5. Re:No Offence To The Devs or Firefox by FooBarWidget · · Score: 3, Insightful

      Bah, of all the things that one can complain about, you complain about the version number? I thought version numbers in open source projects don't matter?

    6. Re:No Offence To The Devs or Firefox by dotancohen · · Score: 4, Informative

      I thought version numbers in open source projects don't matter?

      Evens are stable, odds are not. Point-point releases are bugfixes, and point releases add functionality. Major version releases include major UI changes and break backwards compatibility.

      FOSS versioning is important, but Mozilla does not follow it.

      --
      It is dangerous to be right when the government is wrong.
    7. Re:No Offence To The Devs or Firefox by Goaway · · Score: 4, Informative

      That's the policy of a handful of projects. There's no such thing as an official "FOSS versioning", and if there was, what you described would not be it.

    8. Re:No Offence To The Devs or Firefox by smittyoneeach · · Score: 2, Informative

      Well, if it fixes that tendency to crash the browser if I close a Gmail tab, I'm all for it.
      Switching Gmail to BasicHTML and then closing the tab preserves the session. And this ugly baby is easily repeated. Saw bug reports on both Ubuntu and Gentoo about this.
      I dunno if it's FF3.0 proper, or the half-dozen extensions (which performed flawlessly under 2.0.14), but it sure is annoying.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    9. Re:No Offence To The Devs or Firefox by MMC+Monster · · Score: 3, Insightful

      Remember that version numbers are more of a marketing issue than a coding issue.

      After all, where is Windows NT v1.0 and 2.0?

      --
      Help! I'm a slashdot refugee.
    10. Re:No Offence To The Devs or Firefox by EvilRyry · · Score: 4, Funny

      After all, where is Windows NT v1.0 and 2.0?

      See OS/2.

    11. Re:No Offence To The Devs or Firefox by David+Gerard · · Score: 2, Interesting

      What's your extension load? I've been running FF3 since January, as Minefield nightlies, on XP and Linux, and haven't seen anything of the sort.

      --
      http://rocknerd.co.uk
    12. Re:No Offence To The Devs or Firefox by CrazedSanity · · Score: 4, Informative

      Thank you. I was trying to post the same, but I apparently lost my cookies when I upgraded to FF3. Many projects use the {Major}.{Minor}.{Bug/Service Release} model, pretty much as described, but many only appear to use the model. For some, the second digit is the major version.

      --
      Sanity is like a condom: rather have it and not need it, than need it and not have it.
    13. Re:No Offence To The Devs or Firefox by kat_skan · · Score: 5, Funny

      Okay, so where is OS/1, smart guy?

    14. Re:No Offence To The Devs or Firefox by gnick · · Score: 3, Funny

      ...but I apparently lost my cookies when I upgraded to FF3.

      I had the opposite reaction. I admit to tossing my cookies after noticing the memory usage that FF2 was inflicting, but upgrading to FF3 wasn't in the least bit nauseating - Actually kind of pleasant.

      --
      He's getting rather old, but he's a good mouse.
    15. Re:No Offence To The Devs or Firefox by Anonymous Coward · · Score: 2, Funny

      DOS

    16. Re:No Offence To The Devs or Firefox by BenoitRen · · Score: 4, Informative

      Actually, Firefox 1.0 to 1.5 was just as big a leap as Firefox 2 to Firefox 3 was. Both had a brand-new, much-improved Gecko version, the core of the web browser.

      • Firefox 1.0 - Gecko 1.7
      • Firefox 1.5 - Gecko 1.8
      • Firefox 2.0 - Gecko 1.8.1
      • Firefox 3.0 - Gecko 1.9

      Firefox 3.1 will be based on Gecko 1.9.1. Firefox developers just like to play with the version numbers.

  2. Acid 3 by Spy+der+Mann · · Score: 3, Funny

    Let's hope the Mozilla devs get the Acid3 test to work with Firefox 3.1.

    Well, I can dream, can't I?

    1. Re:Acid 3 by Rhapsody+Scarlet · · Score: 4, Informative

      You can keep dreaming. While Firefox 3.1 is certainly going to improve on Firefox 3.0 (Firefox 3.0 gets 71/100, Firefox 3.1 pre-alpha 1 gets 80/100, I predict Firefox 3.1 final to get 80-90/100), the aim to make changes drastic enough to make Firefox 3.1 pass Acid3 and the aim to get Firefox 3.1 released in a Q4 2008/Q1 2009 timeframe are plainly incompatible. I'd expect Acid3 to pass in Firefox 4.0 myself. Shouldn't be much of a surprise given how long it took Firefox to pass the Acid2 test, but then that never stopped us from using it. ;-)

    2. Re:Acid 3 by hedwards · · Score: 5, Insightful

      I'd really rather they focus on important things first. The Acid tests are specifically much harder than what a browser needs to handle to do a good job with web browsing, in fact a few of the tests specifically use broken code IIRC.

      Really the updates to the bookmark system scheduled for 3.1 are probably going to make a bigger impact on most users than Acid compliance would.

      I think the main point of getting 3.1 out there is to get the features in that couldn't be completed for 3.0 but weren't necessities. And with the level of rebuilding that 3.0 required it's not a shock that a few less important features would have to be dropped to get the important stuff finished.

    3. Re:Acid 3 by mdew · · Score: 3, Interesting

      80/100 on the current nightly builds, http://img176.imageshack.us/img176/7533/acid3trunkok0.jpg

      --
      http://www.fanboy.co.nz/adblock/
    4. Re:Acid 3 by Jellybob · · Score: 4, Insightful

      I would agree, but they HAVE to shoot for Acid 3 compatibility for the next release or browser nerds will be up in arms and it will be a huge PR problem.


      It'll only be a PR problem in the small circle of "browser nerds", everyone else will just get on with their lives, having realised there's more to life then what score your favourite browser gets in the Acid 3 test.

    5. Re:Acid 3 by Goaway · · Score: 5, Insightful

      The Acid tests are specifically much harder than what a browser needs to handle to do a good job with web browsing, in fact a few of the tests specifically use broken code IIRC.

      The things tested by ACID3 are not in general use because browsers don't reliably support them. Many would be in use if they were actually supported. That is the aim of ACID3, to drive browser makers to actually fix these things so people can finally start using them.

    6. Re:Acid 3 by n0-0p · · Score: 2, Informative

      Acid3 is a dumb test. Acid1 and Acid2 tested against a number of dependencies and special cases to ensure broad compliance with the standard. That's what made them useful tests.

      In contrast, Acid3 is a hodgepodge of features from different standards that are broken or unimplemented in different browsers. It lacks the coherence of the earlier tests. That means you can game it pretty easily by implementing one small part of a standard while not having a genuinely useful implementation. In fact, that's what several browser vendors are doing.

      Instead of randomly picking features from HTML, CSS, SVG JavaScript, and SMIL, Hixie should have done an Acid-style test for each standard. That would make it a lot more useful, like the previous Acid tests.

  3. Useless summary by Anonymous Coward · · Score: 2, Insightful

    They could change the version number and release a production-quality 3.1 tomorrow. What matters is the new features/bugfixes/optimizations in 3.1. Without them there's no context for the news.

    1. Re:Useless summary by Kinky+Bass+Junk · · Score: 4, Funny

      For some strange reason, you are required to RTFA.

      --
      Anonymous Coward
  4. Can't blame them... by RuBLed · · Score: 4, Funny

    In every release, they would be given a cake.

  5. Re:Why? by Vectronic · · Score: 4, Informative

    6 months isn't "quick", its only the Alpha in a month...that's about normal for most smaller software, especially for a point (*.1) update, this isn't Firefox 4.0.

    Hell, Opera released 9.51 RC1 (now on RC2) just a few days after 9.5...

    Its pretty normal as far as I see it, and I'm glad they are (or seem to be) returning to a more consistent release schedule, it may eventually become my default browser again, which it hasn't been since Phoenix.

  6. And after Firefox 3.1 by NovaHorizon · · Score: 5, Funny

    Comes Firefox 95!

    1. Re:And after Firefox 3.1 by NitroWolf · · Score: 2, Funny

      Comes Firefox 95!

      Nope, it will be 3.11 and FWG... THEN we can get to 95, though I'm probably going to wait until FF98 if past experience is a guide.

  7. Re:Cake? by ya+really · · Score: 2, Funny

    At this rate, Microsoft better start working on the next cake!

    MSIE developers already figured out the cake is a lie long ago.

  8. Re:Firefox 3.0 is crash happy by Linker3000 · · Score: 4, Informative

    Have to agree - not sure if its add-on related but since I updated several PCs to FF3 I have had about 2-3 browser crashes a week and one UK grocery shopping site makes FF3 just 'disappear'.

    --
    AT&ROFLMAO
  9. There is no such thing as a quick Firefox release. by Cochonou · · Score: 5, Insightful

    Firefox 2.0 was also supposed to be a quick development, based on the same gecko branch. It eventually took about a year.
    I think the past record of Mozilla.org has repeatedly shown that it is unable to release a product on time, given the huge amount of testing/fixing iterations that must come before the final release. A Firefox "quick release" will take time, and divert resources from important future projects such as Gecko 2.
    I would have thought Mozilla.org would have finally admitted that the architecture and development model of Firefox is characterised by long maturation times. This is needed to keep up its high quality level.

  10. Schedule has slipped before by Anders · · Score: 4, Informative

    Of course, at one time, Firefox 3 was targeted for a Q3 2007 release.

  11. Re:Firefox 3.0 is crash happy by aussie_a · · Score: 5, Insightful

    I do have add-ons installed and it hasn't crashed once. Aren't anecdotes fun?

  12. Re:There is no such thing as a quick Firefox relea by trawg · · Score: 3, Interesting

    I'm passing up the opportunity to moderate you as 'troll' despite your obvious troll post on the basis that maybe, just maybe, you have some evidence to back up those statements. I'm not sure what bugs you're talking about but I use Firefox all day long every single day and very rarely have any problems.

    I also use an application (MediaCoder) that I believe uses the XUL parts of Firefox seemingly without any problems (other than annoying load times for what should really be a simple control panel thing).

  13. Re:Very high CPU usage by risk+one · · Score: 2, Informative

    Try installing flashblock. Those ads tend to steal a lot of cycles. Worked for me anyway.

  14. Re:End users don't want constant change by Anonymous Coward · · Score: 5, Interesting

    People getting bent out of shape about the address bar is simply absurd. While I admit, the option to turn it off should appear somewhere, if only in about:config, the development team isn't ignoring it's users. I have a feeling far more people LIKE the new address bar than dislike it. I certainly find it very useful at times. I also happen to find the new user interface to be well thought out and designed.

    The "it's only one option in the config dialog" argument is wearing a bit thin. It also demonstrates a lack of understanding on what testing is required for even simple options. Perhaps terms like "decision coverage" and "condition/decision coverage" are meaningless to you, but they are quite important to software testers. Also important is the psychological concept of the paradox of choice in which many people will not make a choice if presented with too many options. I really am quite sick of hearing, "But it's just one little check box in the option dialog." Take a second and think about how many features that has been said about. Then take a second to consider how much your really now about good user interface design and how much research is done in the area of human/computer interaction.

    The changes presented in Firefox 3.0 are actually quite minor when compared to other UI modifications such as Office 2007 or KDE 4. Such drastic language on your part is quite uncalled for. The changes presented in Firefox's front end are, in fact, not for the sake of change but rather for the sake of improvement. I hope comments like yours don't encourage the developers to stagnate on a single UI design because every time they work to improve it, a vocal minority of rigid people can't pull a stick out of their ass.

  15. Re:Firefox 3.0 is crash happy by imbaczek · · Score: 4, Informative

    IME usually it's flash. install flashblock or noscript and enable only those flash movies you really want to see - haven't seen ff3 crash since I started doing that.

  16. Re:There is no such thing as a quick Firefox relea by Rhapsody+Scarlet · · Score: 4, Informative

    I hope to see the html 5 video support added for Fx3.1

    You're almost certainly going to get it, with Ogg Theora support at the very least (a DirectShow backend for Windows, QuickTime backend for Mac OS X, and GStreamer backend for Linux are also in the works). But the real question that no one seems to be asking is, where is HTML 5 audio support? It's just as much a part of the specification, and Ogg Vorbis is well-known enough that corporate entities aren't so worried about patents. I've seen some work on it recently, but I'm not sure it's mature enough to make the deadline. HTML 5 audio and video support in Firefox 3.1 would be a dream though. Safari already has at least some support for both, and Opera has partial support for audio with video surely not far off. Internet Explorer is obviously going to take a long time to catch up, but I guess we can't have everything...

  17. Re:Why? by dotancohen · · Score: 4, Funny

    After reading the article (a novel concept for slashdot I know), the answer to both your questions is "Yes".

    Which both of his three questions?

    --
    It is dangerous to be right when the government is wrong.
  18. Re:Firefox 3.0 is crash happy by compro01 · · Score: 2, Informative

    Flash sites?

    Only times I've had firefox 3 go down is on particular, badly made, flash-based sites, when trying to do specified things, which makes me fairly sure it's Adobe's fault.

    --
    upon the advice of my lawyer, i have no sig at this time
  19. Re:What's after Firefox 3.1? by dotancohen · · Score: 4, Funny

    Nah, just kidding. Don't take it seriously. :-)

    Fuck, and I was already registering the domain names to squat...

    --
    It is dangerous to be right when the government is wrong.
  20. Re:Very high CPU usage by deek · · Score: 2, Informative

    I see something similar as well. I use linux and Firefox 3 on my work laptop, and at home while browsing www.smh.com.au, cpu will hit 100% and the browser becomes barely usable.

    Interestingly enough, at work, I can browse www.smh.com.au without any issues.

    I noticed that the stop button is clickable during the 100% cpu periods. When I click it, and it eventually registers, the cpu usage plummets back to regular levels.

    I suspect there's some DNS shenanigans going on, because the DNS service at home can be flaky, and I noticed "looking for" like messages in the Firefox status bar. Firefox 3 most likely burns the cycles in some polling loop when waiting for responses to DNS requests.

    Anyway, that's my theory. It's strange though, that only one site manages to trigger the behaviour for me.

  21. Re:Very high CPU usage by Ravadill · · Score: 2, Informative

    Adblock with large filtersets tends to bog down on slashdot because the sheer amount of text/code it has to work through on each page (especially with the new comment system enabled) try disabling adblock to see if it helps.

  22. I wish they would fix the CPU hogging bug. by Futurepower(R) · · Score: 4, Insightful

    "Well, I can dream, can't I?"

    I dream of a Firefox that doesn't have CPU hogging problems. Firefox 3 seems to be a little worse than the previous version.

    For those of us who open a lot of windows and tabs and leave them open a long time, as when doing research, Firefox is a hassle. It slows the entire computer until all windows and tabs are closed.

  23. Re:End users don't want constant change by dlevitan · · Score: 2, Interesting

    I have a feeling far more people LIKE the new address bar than dislike it.

    I'm one of the people who, for the most part, really likes the new address bar. Being able to type in a site's title to get to the url is a great time saver for me. However, there is one thing I can't stand about it, which is that sometimes it takes a second or two for it to load (especially if I'm on battery power and the hard drive is spun down) and in the meantime firefox freezes. If they could just sort that problem out I'd be very happy.

  24. Re:End users don't want constant change by ikkonoishi · · Score: 2, Insightful

    Try playing around with "browser.urlbar.search.chunkSize" and "browser.urlbar.search.timeout" in about:config. The prefs file says this about it.

    // Size of "chunks" affects the number of places to process between each search // timeout (ms). Too big and the UI will be unresponsive; too small and we'll // be waiting on the timeout too often without many results.

  25. Re:End users don't want constant change by Anonymous Coward · · Score: 2, Insightful

    "Kindergarten interface" is probably the most subjective complaint possible on the matter and last time I checked, kindergartners don't write in a sans serif font face. If you're referring to multiple colors, there is scientific research to support such a change, but then again you consider research to be garbage so I don't see you taking much stock in that.

    It's also interesting how you reiterate "Change for the sake of change isn't good" with no new content despite that very point having been dealt with in the parent (repeating the same point verbatim is not actually a rebuttal). Despite what you may think, you have not successfully argued that these changes were made for the sake of change (they were not, any such statement is clearly ignorant and closed minded) or that the changes were actually negative. All you've done is described why YOU don't like it in the vaguest possible terms you could manage. I assure you, you are a minority and a small one at that.

    While I don't have a problem with your personal taste in web browsers, I do find your critiques to be more of insults rather than critiques. If you don't like Firefox 3, that's fine, but making ignorant statements is a hard position to defend. I challenge you to provide actual evidence that suggests the user interface in Firefox was changed solely for the sake of change.

    Just to be technical, there is an algorithm for what to display based on what you have typed. It is anything but random.

  26. WHAT? by nx6310 · · Score: 2, Funny

    So more add-on incompatibility?! I want my Develpers Add-on to work again, not another!?

  27. Just kick flash out by DrYak · · Score: 4, Informative

    Just kick out the damn buggy Adobe Flash plug-in.
    It runs in the same process as Firefox :
    It eats to much memory, slows too much the browser, and take the whole browser down with it.

    Either disable it, or at least use adblock+ and noscript to avoid having 80 flash widgets running inside your 30 tabs.

    --
    "Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
    1. Re:Just kick flash out by atamido · · Score: 3, Informative

      Either disable it, or at least use adblock+ and noscript to avoid having 80 flash widgets running inside your 30 tabs.

      What you want is FlashBlock.

  28. Already using latest Adblock Plus and NoScript by Futurepower(R) · · Score: 2, Insightful

    I went to Tools/ Options/ Applications/ and selected "Always ask" or "Save File". I will try that. It's necessary to do that carefully, because the selection box is buggy.

    I was already using the latest Adblock Plus and NoScript versions.

    I don't think Google is getting much software development for the $50,000,000 each year it is paying.

  29. A good idea by Monoman · · Score: 2, Interesting

    It would be great if the Firefox team could release updates on a schedule ... I know, I know it is a crazy dream.

    But think of it this way. Release the incremental updates (.x) every quarter or six months and release them on time. Release version updates every 12 -24 months, up the the FF team, but stick to the schedule. If the FF team could do that it would show constant improvement and drive MS nuts.

    Isn't this how the Ubuntu team operates? I know it is an apples to oranges comparison but I think it could work. There is no way MS could keep up with a consistent release schedule.

    --
    Keep the Classic Slashdot.
  30. Re:Why? by Junior+J.+Junior+III · · Score: 2, Funny

    That both.

    --
    You see? You see? Your stupid minds! Stupid! Stupid!
  31. Re:Yes, faster, but the CPU hogging bug is there. by Goaway · · Score: 2, Informative

    Once again, are you sure that's not just Flash?

  32. Re:End users don't want constant change by clickety6 · · Score: 2, Insightful

    People get "bent out of shape" because something that worked well for them has been taken away and replaced with something that (for them) works less well, is less intuitive (when I'm in a URL entry box, I don't expect to have searches on titles), looks awful (that two line layout is not nice to read, despite having pretty colours) and does not allow a return to old functionality. If "awesome bar" had been an option, then there wouldn't be a fuss. But the developers seem to have decided they know what is best for the users and because they have made this great new thing it should be shoved down their users' throats. Last time I had this happen to me was Clippy - but at least you could turn that wonderful new functionality off!

    As we can customise the interface, the awesome bar could exist alongside the address bar so that you could drag one or the other into your interface to use.

    --
    ----------------------------------- My Other Sig Is Hilarious -----------------------------------
  33. Re:Firefox 3.0 is crash happy by EvilRyry · · Score: 2, Informative

    Flash runs inside of the Firefox process. They die together. On a side note, I've been running Firefox 3 on 3 Ubuntu machines and a Windows machine without any crashes so far.

  34. Re:Firefox 3.0 is crash happy by CrazedSanity · · Score: 2, Insightful

    I've installed several add-ons and it hasn't crashed for me, either. I thought it would be just as stable on any other OS, so I installed it on my mother's tablet (with M$ Vista), and it crashed almost immediately. Every once in a while, it'll randomly crash when I hit F6 (to highlight the URL), or when I first browse to a site. I would venture a guess, based upon my admittedly limited amount of experience on the matter, that the Windows version may have more instabilities than that of Linux... gosh, imagine that. ;)

    --
    Sanity is like a condom: rather have it and not need it, than need it and not have it.
  35. Re:Firefox session manager doesn't work. Buyers .. by mysticgoat · · Score: 2, Insightful

    It seems your usage is so far removed from both

    • designed use of the browser
    • common de facto user requirements

    that I don't see why a browser should be expected to perform well against your criteria.

    FF is open source, so it would be a simple enough thing for you to either fork it yourself or hire someone with the skills to do so, and build a variant that could be left running for days on end, with hundreds of tabs left open.

    But I'm not sure that the community needs a browser that meets these requirements. Maybe I'm wrong, in which case I expect this post to get soundly trounced.