all 13 comments

sorted by: hot top controversial new old
[–] 22 points 1 month ago

Maybe they should drop the AI and go back to 4.

  • source
  • [–] 17 points 1 month ago (1 child)

    From 4-week to 2-week:

    We are planning to move Firefox Desktop and Android from a 4-week release cadence to a 2-week release cadence starting in September 2026.

  • source
  • hideshow 2 child comments
  • [+] 14 points 1 month ago* (last edited 1 month ago) (1 child)
  • [–] 9 points 1 month ago

    I don't see why it's necessary for any software. I understand if companies want to release security patches and bugfixes faster. But those releases are usually accompanied by way too many unnecessary changes driven by marketing/product that a lot of people don't give a shit about.

  • source
  • parent
  • [–] 13 points 1 month ago

    But why... I don't even fully get why there is a dedicated cycle anyways. Just release an update when there is something worthwhile.

  • source
  • [–] 5 points 1 month ago

    They already produce nightly builds. Why are people upset that they feel confident to release stables every two weeks?

  • source
  • [–] 4 points 1 month ago

    Fast release cycles might make sense for a new project that is in rapid development.

    Fast release cycles for established products make no sense. What I want from a project that is tens of years old is primarily stability. They can do their internal releases at whichever pace they want, but don't push on users updates this frequently, it's just wrong.

  • source
  • [–] 2 points 1 month ago

    This will be OK with me, as long as I don't have this popping up on a regular basis, forcing me to restart my browser:

    image

  • source
  • [+] -8 points 1 month ago (1 child)

    FF is always updating already, yet another reason to switch.

  • source
  • hideshow 2 child comments
  • [–] 5 points 1 month ago* (1 child)

    You mean from your 4-weeks-cycle browser to any other one, which are all (through being based on Chrome) on 2-weeks-cycles? Or they're intentionally lagging behind their upstream, which is the exact same only with less control as you simply choosing not to update your FF if an update is available?

  • source
  • parent
  • hideshow 2 child comments