Short release cycles mean smaller deltas and it also makes postponing the merging of changes to the next release is less disruptive. Merging things when they are ready instead of merging them to early to not miss some big releases is better.
Another reason smaller deltas is better is that risk does not scale with a linear relation relative to the amount of change but more like a quadratic or exponential relation. So, the less changes you introduce with a release, the less effort you need to ensure all is well. The testing over head increases massively with the amount of change since there are more combinations of things that can go wrong that all need testing. Finally, with the time increasing between the introduction of issues and people finding them, the complexity of analyzing them in the presence of other bugs becomes harder. Shorter feed back cycles are great for finding issues early.
Currently from nightly to release takes about 12- 16 weeks (assuming 6-8 week cycles). With this change, it will reduce to about 8 weeks. That's still two months of exposure to large group of nightly testers and an even larger group of beta testers.
Even if that weren't true, though, rapid release means a lot more updates, and updates are a pain in the butt.
Of course, you need an extensive battery of unit tests and integration tests, and lots of user testing in beta. But actually if you're only deploying smaller self-contained changes then there's less moving parts at any given time. You'll have stronger guarantees of less interactions.
Quite often, missing those sorts of improvements isn't a big deal. That depends on the nature of the software in question, though.
https://support.mozilla.org/en-US/kb/choosing-firefox-update...
Done poorly, or even in a mediocre fashion, and we've got more half-baked features and insufficiently-tested changes.
Now, which scenario is more likely?
1) People rush to get things into release because if they miss the release, they are waiting longer to get it out. If the release is every 4 weeks, a missed release is not as big a deal.
2) Long release cycles means things done early in the release get forgotten, so when it's finally released, they tend to be off people's minds.
3) Larger releases become harder to update and deploy. Larger file sizes, a lot more changes all at once.
As someone who has done both (long and short release schedules) I can't imagine going back to long release schedules. It has a lot more complexity and is a lot more error prone than a shorter release schedule. Not only do you get the practice, but people are more inclined to wait until next release to get it right.
Plus, most of the serious bugs are found right away when a new group of users starts testing, e.g. when Firefox Nightly version moves to Beta or Beta moves to stable Release. Firefox Nightly, Beta, and Release channels have very different user populations. They have different hardware (Nightly users are power users with big, fast machines), software (Release users are more likely to use anti-virus software or not have the latest GPU driver updates installed), and browsing usage.
Mozilla's studies of crash rates and bug fixes for Firefox Beta showed that most of crashes and bugs are seen in the first two weeks or so. Having more beta "bake time" with a very long beta cycle has little benefit after the first batch of bugs are found and fixed.
An interesting historical tidbit: about 60% of Firefox Beta users are in India and Indonesia. That is definitely not representative of Nightly or Release user populations! The apocryphal story is that many years ago, a local computer retailer started passing around copies of a beta CD of Firefox 4 so people didn't have to download it over a slow or metered internet. And then all those people are still on the Firefox Beta channel.