Slashdot Mirror

← Back to Stories (view on slashdot.org)

Firefox 1.0.7 Released

Posted by ryuzaki0 on from the download-now-if-you-are-in-korea dept.

hackajar writes "Firefox 1.0.7 has been released today. From the announcement "Fixes are included for the international domain name (IDN) link buffer overflow vulnerability and the Linux command line URL parsing flaw. There are also other security and stability changes, including a fix for a crash experienced when using certain Proxy Auto-Config scripts. In addition, some regressions introduced by previous 1.0.x security updates have been resolved.""

4 of 366 comments (clear)

  1. Premature announcement ? by MerlynEmrys67 · · Score: 0, Redundant
    I hit the check for updates button in the options...

    I get Firefox was unable to find any updates for my 1.0.6 firefox installation.

    Oh well - time to get P0wed

    --
    I have mod points and I am not afraid to use them
  2. Re:And yet..... by iamjoltman · · Score: 0, Redundant

    They always release the update on their servers, and wait a couple days to release it via the arrows. The do it to reduce load on their servers

  3. An update problem... by RUFFyamahaRYDER · · Score: 0, Redundant

    I'm just wondering if anyone has the same problem as I'm having... In Firefox I click TOOLS->OPTIONS->ADVANCED. Then I click on software updates and click "Check Now" but it doesn't see the new Firefox version... Anyone know what is going on with this?

    For now I'll get it here...

  4. Branches and trunks by Anonymous Coward · · Score: 0, Redundant

    If Mozilla Firefox 1.0.7 was just released... Then what was Mozilla Firefox 1.5 Beta 1?

    It was a release of the 1.5 branch (which could be the trunk?) of FF. 1.0.7 is a release from the 1.0 branch of FF. On any large software project, it is common to "branch" (make a snapshot) of the source tree when you are planning on doing a release. This allows you to isolate code changes (typically you only want bug fixes going into a release candidate branch while new functionality is allowed to continue in the main trunk). Like I said, this prevents potentially de-stabilizing new features from getting into your releases.

    This does present a bit of a hassle though, as often times you will have to fix bugs in the branches as well as the trunk, so it creates more work in that regard. But on large projects with lots of developers, this really is the only workable solution.