3 ms·
It actually does the opposite. It's big, infrequent releases that are risky, less stable. Users update automatically; they barely notice it today. Most non tech
by jillesvangurp 7y ago
It actually does the opposite. It's big, infrequent releases that are risky, less stable. Users update automatically; they barely notice it today. Most non techie users have no idea that it is happening. A few years go we had these big bang releases with browsers, operating systems, etc. and things were much worse. Anytime you unleash millions of new lines of code on users it's almost guaranteed that there will be some stuff wrong with it that your months or years of testing did not catch.
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.
- JohnFen 7y agoYes, I'm well aware of the arguments in favor. It's just that I don't see it playing out much in the real world. In my experience (on the whole -- there are exceptions), rapid released software tends to be of lower quality. Even if that weren't true, though, rapid release means a lot more updates, and updates are a pain in the butt.
- nickm12 7y agoCan you give concrete examples? For the software I use that is on a rapid release schedule, (Firefox, Chrome, Dropobox, probably others I'm not even aware of) I don't notice any sort of quality issue. The only "pain in the butt" is having to restart my browser.
- nickm12 7y ago+1. Another benefit of rapid releases is being able to release major refactors behind feature gates. This approach was taken when Mozilla shipped an mp4 parser written in Rust [1]. By having rapid release cycles, they could spend a cycle or two verifying that the new component produced identical results "in the wild" before enabling it by default. If they had 1-year release they never would have been able to verify their implementation at such a scale. https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/ https://hacks.mozilla.org/2016/07/shipping-rust-in-firefox/