Recommended Posts

Wow, a candidate for a Beta :rolleyes: When are they going to release the candidate to the candidate of the Beta? :laugh:

  • Code Freeze: 11/04
  • Builds Start: 11/04
  • QA: 11/04 - 11/09 (estimate)
    • Smoketests and BFTs using Mozmill: (1 person)
    • Manual smoketests, BFT areas, and Other OS Spot Checks: 11/04-11/09 (3 people)
    • Testday: 11/05 (3 people monitoring)
    • Accessibility: On-going (1 person)
    • Top Sites Functionality and Page Load Testing: Before 11/09 (1 people)
    • Updates checks: Before 11/09 (1 person)
      • Manual spot checks as necessary

Seems like tuesday is the day (in Indian system , it would be called 9/11)

Although i have been using Minefield on my very old Office PC and only Beta 6 on my home PC. Beta 7 makes using Firefox on my Home PC enjoyable again.

For now, the speed difference is no longer substantial between Firefox and Opera / Chrome. Page Rendering and JS are still little slower. But i cant live with that, for all the great extensions and awesome bar.

Hello,

As I just D/L and installed the FF4.0b7 RC1 build, but was curious as I wanted to update my sig @mozillaZine Forums--->it use to be:

Mozilla/5.0 (Windows NT 6.0; rv:2.0b6) Gecko/20100101 Firefox/4.0b6

However now when I go to help--->About

resizedmm.jpg

Uploaded with ImageShack.us

Any ideas where a 'string would be'...? lol

Any ideas where a 'string would be'...? lol

It's stupid that they removed the string from the about box, but you can still see it by typing

about: in the urlbar.

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101106 Firefox/4.0b8pre

It's stupid that they removed the string from the about box, but you can still see it by typing

about: in the urlbar.

Build identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101106 Firefox/4.0b8pre

Thanks crispkreme...:) It was getting me kind of annoyed on this nice Saturday afternoon...lol! I could not find it anywhere...

Note: the build strings in main releases (beta, final) will always show Gecko/20100101 now, to avoid 'fingerprinting'.

You answered my next question...lol

As I was wondering why the Beta 4.0 builds showed Gecko/20100101, with (IIRC) Beta 1, 2, 3, 4, 5, and 6..

Thanks Kirkburn

Note: the build strings in main releases (beta, final) will always show Gecko/20100101 now, to avoid 'fingerprinting'.

People were using it as a version identifier for some strange reason, random sites would break every year since they didn't expect the year increase of nightly builds and such.

By freezing it on a set date, they'll force those people to either update their code, or make it never have an issue again (unless they then remove the fake date which I think is the general plan)

People were using it as a version identifier for some strange reason, random sites would break every year since they didn't expect the year increase of nightly builds and such.

By freezing it on a set date, they'll force those people to either update their code, or make it never have an issue again (unless they then remove the fake date which I think is the general plan)

hmm shouldn't they just do it in one go rather than risking two potential breakages?

Taken from buildnotes page. Here is what is left to be done before beta 7.

Final checks before push

Virus check

Update Bouncer

Push to mirrors

  • Wait for email from driver before continuing

Final verify

Push snippets to beta channel

Remove index.html files

Release

Will Beta 7 be the first one with JaegerMonkey? I've been using the nightlies so I haven't kept track of the milestones that well.

Yup.. if no blockers are found. Beta 7 should be released within the next couple of days. looking forward to beta 7 myself.

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

    • No registered users viewing this page.
  • Posts

    • No, "a great deal" for 32GB of DDR5 is $50, not $350. I mean I see what you mean, that it's a decent price compared to what's currently available, but you really should put a disclaimer in this articles explaining that it's still multiple times more expensive than it used to be.
    • Linux 7.1 stable launch looms as Linus Torvalds releases the final release candidate by Paul Hill Linus Torvalds has just released what’s expected to be the final release candidate of Linux 7.1, rc7. The Linux founder said that this RC is not small, but smaller than recent releases, which is a good sign because he expects the stable version to drop next week if things continue on this trajectory. Linux kernels see a merge window for the first two weeks of their life, where developers add new features, then there are about seven or eight weeks of release candidates before the stable version. Typically, there are seven release candidates, but if more time is needed, then an eighth release candidate is released too. This week’s RC’s biggest area of fixes was for GPUs, with networking just behind. Torvalds said that the rest of the release was “pretty random and spread out” with some architecture fixes, driver fixes, filesystem improvements, and build fixes for more unusual configs. In terms of specific pieces of hardware receiving improvements in this update, we had more AMD Zen6 models supported and fixes for AMD SDMA 7.1 and GFX11. Hardware that got improvements includes Lenovo laptops, HONOR laptops, and MSI laptops. Here are the changelogs for those: ASoC: amd: acp: Add DMI quirk for Lenovo Yoga Pro 7 15ASH11 Input: atkbd - add DMI quirk for Lenovo Yoga Air 14 (83QK) Input: atkbd - skip deactivate for HONOR BCC-N's internal keyboard ASoC: amd: yc: Add MSI Raider A18 HX A9WJG to quirk table ASoC: amd: yc: Enable internal mic on MSI Bravo 17 C7VF When the stable Linux 7.1 is released, it will be up to distribution maintainers, such as Canonical and Red Hat, to release the update to their users via the update manager. Some versions of Linux will get it before others, and some will never get it at all. Fedora and Arch-based distros will be among the first to get it, though. If you don’t get it, the security fixes will be backported to your system’s kernel, so you won’t be at risk, but you won’t get newer hardware support, which is fine if your computer works now.
    • Ideally, the algorithm is smart enough to see the real sender ID and non-spoofed address to block it. Ideally.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      249
    3. 3
      Steven P.
      71
    4. 4
      ATLien_0
      68
    5. 5
      +Edouard
      68
  • Tell a friend

    Love Neowin? Tell a friend!