That’s nice and all, but I don’t really understand how that helps.
Ah, from the article:
> some “testers would go days without a livable build, so they wouldn’t really have a handle on what’s working and not working,” the person said. This defeated the main goal of the testing process as Apple engineers struggled to check how the operating system was reacting to many of the new features, leading to some of iOS 13’s problems.
I think the idea is that you can't put anything with a known regression in the daily builds any more. But that gives a problem of how do you even get feedback on an in-development feature while you're trying to get it to a zero-regression state? The answer appears to be feature flags, I guess.
So one of the issues is that Apple lives on their own tools, so when critical system components are broken nobody can get work done. But ideally they'd actually fix the bugs and try to keep the daily builds livable rather than trying to sweep the issues under the rug…
The problem seems to be there are so many bugs it becomes impossible to tell what caused what. Also, mixing unfinished features with known bugs in there might be a waste of time.
Ah, from the article:
> some “testers would go days without a livable build, so they wouldn’t really have a handle on what’s working and not working,” the person said. This defeated the main goal of the testing process as Apple engineers struggled to check how the operating system was reacting to many of the new features, leading to some of iOS 13’s problems.