I just read the weekly update. There is a glaring communication problem, not between Bungie and the community, but between teams inside of Bungie. I've been in IT for a while now (to be clear i'm not claiming that what i do is anything like building a game). We at least, at the very least, communicate with other teams that we work with. We share our data on network drives that all relevant people can access. When I submit patches, software, and changes for QA, I also have to provide the INTENDED patch/change notes. Having a change approval board, and QA process that include a "cut sheet" if you will, is best practice for a reason. I think a serious evaluation of your current QA processes should be on top of that list. Even before new content and massive DLCs. I'm not claiming that mistakes are never made, and shouldn't be expected. I'm just saying that completely leaving QA to verify itself with it's own design is flawed. (This meaning that QA verifies the patch by how is performs according to it's own code is a bad idea) Patch notes represent an approved change, those notes is what the patch should have been tested against. Not only did this make it past Bungie QA, Sony and Micro$oft completely missed it as well. Here are my suggestions. Patches need to be tested not only using the code/data in the patch. They also need to be tested against the intended/approved change. I'm sure there a many unproductive meetings at Bungie HQ (everyone has them), Thoroughly explain to other relevant teams what's going on. Share your data with them. A copy pasta of a few lines of code to share among colleges is not a security problem. If you don't have a proper CAB, make one. Slow down, be deliberate, take a little extra time. You know as well as I do. 1 well built, tested, deployed patch/change, is much much cheaper to produce (no matter how much the development cost may be). Than slapping together 1 patch and getting it out the door. Then spending additional development time, QA time. A few times over to develop patches for your patches.