Actually, Dolphin Emulator is a good example what happens with huge releases - there are too many changes to test them properly, so devs avoid to make stable releases, and users are forced to use nightlies because they have no real alternatives (a latest stable 5.0 release was released in 2016). Technically, it is close to the rolling updates system, which we, IIRC, do not want to use with OpenMW.AnyOldName3 wrote: ↑11 Feb 2020, 10:15 A lot of things there are only true if you make them true. For example, Dolphin Emulator hasn't had a stable release for several years and doesn't intend to have another any time soon.
There are build artifacts only for Windows, and I am not sure if anyone really tests every pull request using these builds before it get merged to master.AnyOldName3 wrote: ↑11 Feb 2020, 10:15 Users are expected to use builds from the master branch, and CI artefacts from pull requests are the things for the lab rats. That works out fine while violating a lot of the things you said as fact.
On other platforms testers have to build pull requests themselves, and I am not sure if testers check every pull request as well.
Who is supposed to check if every of 260 tickets from the 0.46 release works properly and does not cause new issues (to claim the 0.46 to be a bug-free and give us a green light to release the 0.46), and which amount of time such check would require?
From what I can tell, we use the "a game launches, a quick test does not show critical bugs" check before release instead, and it does not guarantee that users will not encounter bugs which were not present in previous release.