Recommended Posts

It's been decided that the next major official release of Firefox will be version 1.5 instead of version 1.1. This does not affect the release date of September and changes nothing at all except the versioning number. This change is due to the significant increase in features and stability that the versioning deserves an increase. I'll post official statements later but for now here is the new roadmap

Roadmap

I'll update my 'Road to Firefox "1.1" bug report' later tomorrow along with the graphs. (see sig for that information)

For the last several months, we've been discussing the versioning of the upcoming Firefox release.

One major consideration in this decision was that the sheer volume of changes in the Firefox core (Gecko) made a minor .1 increment seem misleading. While it may not be obvious by looking simply at release dates, today's Gecko core of Firefox has seen nearly 16 months worth of changes compared to what shipped in Firefox 1.0. This is because we created our Gecko 1.7 branch (the branch from which Firefox 1.0 shipped) back in April of 2004. At that time, Gecko development on the trunk continued and very little of that work was carried over to the 1.7 branch to be included in Firefox 1.0.

Another consideration was that we've made some major improvements to the Firefox application, especially in the update and extension systems that warrant more than a minor version bump. Calling it 1.1 would suggest to most users that this was a minor update when in fact it is quite major and all 1.0 users really should move forward for a much improved product.

Source: Asa Dotzler's Blog

Edited by supernova_00
Link to comment
https://www.neowin.net/forum/topic/346988-firefox-11-scrapped-15-it-is/
Share on other sites

Interesting... though I think it is a logical move. I look forward to the improved update system, as redownloading the entire file is inefficient and impractical - other than that Firefox is fine already.

What version will be the next Thunderbird? 1.1 or 1.5?

So there will not be Firefox 2.0 based on Gecko 2.0 (regarding the last plan for Firefox 1.5 with Gecko 1.9)

Now we will have Firefox 1.5 based on Gecko 1.8, maybe Firefox 2.0 with Gecko 1.9, and later next year Firefox 3.0 on Gecko 2.0 (the biggest Gecko release).

Edited by Kalphegor
It's been decided that the next major official release of Firefox will be version 1.5 instead of version 1.1. This does not affect the release date of September and changes nothing at all except the versioning number. This change is due to the significant increase in features and stability that the versioning deserves an increase. I'll post official statements later but for now here is the new roadmap

Roadmap

I'll update my 'Road to Firefox "1.1" bug report' later tomorrow along with the graphs. (see sig for that information)

586245002[/snapback]

I find it sad that somebody like you can be so obsessed with an internet browser. And a mediocre browser at that.

No, I just think its sad that he is such a fan boy, and I mentioned that I don't like firefox.

586246792[/snapback]

Of course he is fan boy but least he knows what is talking about and knows a lot of detail like the bug reports etc nad how the project is unfolding.

The fan boy I hate is OMG< 1337 f1r3f0x rox!

Here is a statement from a mozilla driver:

For the last several months, we've been discussing the versioning of the upcoming Firefox release.

One major consideration in this decision was that the sheer volume of changes in the Firefox core (Gecko) made a minor .1 increment seem misleading. While it may not be obvious by looking simply at release dates, today's Gecko core of Firefox has seen nearly 16 months worth of changes compared to what shipped in Firefox 1.0. This is because we created our Gecko 1.7 branch (the branch from which Firefox 1.0 shipped) back in April of 2004. At that time, Gecko development on the trunk continued and very little of that work was carried over to the 1.7 branch to be included in Firefox 1.0.

Another consideration was that we've made some major improvements to the Firefox application, especially in the update and extension systems that warrant more than a minor version bump. Calling it 1.1 would suggest to most users that this was a minor update when in fact it is quite major and all 1.0 users really should move forward for a much improved product.

Source: Asa Dotzler's Blog

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Apple reluctantly forces strict new age checks on Texas users starting today by Paul Hill Apple will begin enforcing the Texas Age Assurance Law (SB 2420) following a recent court ruling that lifted an injunction on SB 2420. Starting June 4 (today), Apple will enforce strict age-verification and parental-consent rules for new Apple accounts created in Texas. This move will affect children under 18 who go to download apps or attempt to make in-app purchases. Apple previously expressed privacy concerns related to this law, but compliance is now mandatory for the company, nevertheless. Apple will use several APIs to follow the law. Principally, the Declared Age Range API will fetch the specific user age bracket (Under 13, 13-15, 16-17, or 18+) and a verification method. The Significant Change API (PermissionKit) will trigger a system dialog for parental consent if an app gets a major update or an age-rating shift. There is also a new property type in StoreKit that allows developers to automatically check when their app’s age rating has changed on a user’s device and then use the Significant Change API to request parental consent. Finally, App Store Server Notifications can be configured to tell developers when a parent revokes consent, blocking app launches. To ensure they are ready for these changes, developers must immediately use Apple’s sandbox testing environment to validate these APIs in their apps. For any developers out there finding this to be inconvenient, get used to it. Other regions, such as Utah, Louisiana, and Brazil, are looking at, or have implemented, similar rules.
    • They should show the onedrive recycle bin in a searchable manner and on app not just on the website
    • You looking at a phone or something? On my 4K HDR monitor it is frikking spectacular.
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
  • Popular Contributors

    1. 1
      +primortal
      484
    2. 2
      PsYcHoKiLLa
      229
    3. 3
      Skyfrog
      72
    4. 4
      FloatingFatMan
      61
    5. 5
      neufuse
      54
  • Tell a friend

    Love Neowin? Tell a friend!