Recommended Posts

Guys, think about what a Release Candidate is. Why would it say release candidate on a candidate for release? It's intentionally not supposed to change further.

Because that's not the usual method. For every software company other than Mozilla, release candidates cannot become final without rebuilding. I like the way Mozilla does it, but "Release Candidate" usually just means that it's another testing build.

I understand that's the usual process, but sometimes bugs do sneak in and then the program is changed. It would still make sense to say this is the RC version, and then say final or just 4.0 when it's officially final.

If that were strictly adhered to, you'd never release the final, because bugs will always be found.

The idea in Firefox's case is that the RC is when nothing else changes - if a showstopper appears, you make a new release candidate. You don't fix the bug, then put out the final. Bugs found after declaring the RC final are then point releases.

Alpha, beta, release candidate definitions differ from group to group - but the above approach certainly isn't wrong or particularly strange.

an annoying bug in the RC which wasn't there in beta 12 for me:

if you click refresh then click on another tab you have open you can't click on refresh until the previous tab's page has been refreshed, very annoying!

No issue here for me on RC1.

For some reason extensions won't install anymore on my nightly builds, and I have to download the latest nightlies because the auto updater says I have the most current version each time :/

I think I might wipe it when the RC is out and see if that fixes it!

If that were strictly adhered to, you'd never release the final, because bugs will always be found.

The idea in Firefox's case is that the RC is when nothing else changes - if a showstopper appears, you make a new release candidate. You don't fix the bug, then put out the final. Bugs found after declaring the RC final are then point releases.

Alpha, beta, release candidate definitions differ from group to group - but the above approach certainly isn't wrong or particularly strange.

I do think they should emphasize that it's an RC build. There are still people who might think they already have the ff4 just because one of their friends sent them a link from majorgeeks.

And if some showstopper blocker comes up, people will start whining about it blaming it on FF4 (when what they currently have is a test build)

For some reason extensions won't install anymore on my nightly builds, and I have to download the latest nightlies because the auto updater says I have the most current version each time :/

I think I might wipe it when the RC is out and see if that fixes it!

As far as I understand the builds don't update when a release is near.

I do think they should emphasize that it's an RC build. There are still people who might think they already have the ff4 just because one of their friends sent them a link from majorgeeks.

And if some showstopper blocker comes up, people will start whining about it blaming it on FF4 (when what they currently have is a test build)

I would think that if nothing is found, it will actually be shipped as the final build, so without the RC in the About screen!

As far as I understand the builds don't update when a release is near.

Thanks :)

For some reason extensions won't install anymore on my nightly builds, and I have to download the latest nightlies because the auto updater says I have the most current version each time :/

I think I might wipe it when the RC is out and see if that fixes it!

LOL, I thought there really are no updates. So we have to manually install everytime the nightlies is updated? I'll probably wait for the RC then.

is it worth installing the RC on the mozilla ftp or should i wait for it to be officially released

its still showing B12 on the FF4 site

I downloaded the Release Candidate from the Mozilla FTP earlier, and it seems to be running perfectly well for me. Previously, Minefield and the Firefox 4 betas would 'hang' on me for some time, but this doesn't seem to have happened with the Release Candidate yet. Hopefully, it won't happen at all.

is it worth installing the RC on the mozilla ftp or should i wait for it to be officially released

its still showing B12 on the FF4 site

If you can wait a few days more, then wait. a few more days of waiting won't hurt.

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

    • No registered users viewing this page.
  • Posts

    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
    • Thanks for the advice guys, I'll give my current GPU a clean and then run the benchmarks to see how similar it is. Hopefully a bit of a clean-out will help it last a bit longer.
    • Pretty sure those will still be in this game. The series' well-explored psychosis themes will return as well.
    • "performance issues? what performance issues?!"
    • Microsoft making much needed change to Windows 11, 10 Patch Tuesday security updates by Sayan Sen Recently, Microsoft delivered its latest Defender patches for Windows 11 ISOs. These definitions are released from time to time alongside the general security updates available during Patch Tuesday. Speaking of Defender, the company has now announced another important change that affects how security updates are delivered to enterprise devices running Windows. According to a recent announcement, Microsoft Defender for Endpoint's endpoint detection and response (EDR) updates will no longer be bundled with the monthly Windows security updates or Patch Tuesdays. Instead the company is shifting delivery of these updates to Microsoft Update, bringing EDR servicing in line with several other Microsoft Defender components. If you recall, Microsoft last year moved PowerShell updates to Microsoft Update (MU) as well since it provides automatic updates for Microsoft products and services. Thus the move is intended to allow Microsoft to deliver EDR improvements and security enhancements independently of the OS's regular monthly update cycle; this should enable faster deployment of protection updates without requiring organizations to wait for the next Patch release. For those unfamiliar, Microsoft Defender for Endpoint's EDR capabilities are designed to help organizations detect, investigate, and respond to advanced threats across managed devices. Keeping these components updated is critical for maintaining protection against evolving attack techniques. The rollout has already began for Windows 10 devices in late May 2026 (last month) and Microsoft says it will gradually expand support to Windows 11 and the remaining supported Windows versions over the coming months. The company expects deployment across Windows 10 and Windows 11 to be completed by fall 2026 or around Q3 of this year. Once the transition is complete, EDR updates will be delivered through Microsoft Update using KB5005292, provided the required prerequisite updates have already been installed. Microsoft is also introducing a new Defender Update Service as part of the change. Following installation of the first update, devices will automatically create a new directory located at %ProgramData%\Microsoft\Microsoft Defender\Defender Update. Microsoft notes that restarts may occasionally be necessary in case of "rare" failure scenarios. For most organizations, the tech giant says no action will be required as long as Microsoft Update is already permitted within their update management strategy. Admins who rely on manually deployed update packages, however, will need to adjust their processes to ensure the new Defender update package is included. Microsoft also recommends reviewing internal documentation and notifying helpdesk and security operations teams about the updated delivery mechanism to avoid confusion during the transition. As a prerequisite, the tech giant notes that systems must be running Sense version 10.8798.25857.1000 or later and have one of the following Windows updates (or later) installed: Win11 24H2 KB5062660 (2025-07 Cumulative Update Preview) Win11 23H2 KB5062663 (2025-07 Cumulative Update Preview) Win11 22H2 KB5062663 (2025-07 Cumulative Update Preview) Win10 22H2 KB5062649 (2025-07 Cumulative Update Preview) Win10 1809 KB5063877 (2025-08 Cumulative Update) Server 2019 KB5063877 (2025-08 Cumulative Update) Server 2022 KB5063880 (2025-08 Cumulative Update) Server 2025 KB5063878 (2025-08 Cumulative Update) As always, organizations should verify that their update policies align with the new servicing approach before the broader rollout reaches all supported Windows platforms later this year. In case of major problems, the EDR update can be rolled back to the inbox version stored in %ProgramFiles%\\Windows Defender Advanced Threat Protection (ATP) using: MpCmdRun.exe -RevertMde -Product Edr -ToVersion Inbox For those who have access to the Microsoft 365 Admin Center portal, you can view the message here under ID MC1381119.
  • 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
      248
    3. 3
      Steven P.
      73
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!