[skissane]

> Shipping two different versions of the software, instead of having some sort of switch you can flip, seems sub-optimal precisely

Someone on X was saying that NASA's definition of "flight software" includes config files. So it isn't actually the code that needs to be changed, just the config.

I think the need for 4 weeks for a config change is the requirement to test the new config in a simulator (against a long list of scenarios) and have it reviewed and approved by various engineering teams, both Boeing and NASA. Plus likely some margin added.