plott1964 Posted July 8 Posted July 8 I'm curious (and nosey)... When a bug is reported, how does ED handle them? I would assume the standard process is: Bug Reporting and Documentation Prioritization and Triage Root Cause Analysis Testing and Validation Continuous Improvement and Feedback Loop But, my question is more specifically in reference to processes 2 and 3. How are these processes done? How are bugs prioritized? How much RCA is performed and to what detail? PC specs: Intel Core i7-13700K [Raptor Lake 3.4GHz Sixteen-Core LGA 1700] (stock clock)/64.0 GB RAM/RTX 3080 GPU (stock clock)/Windows 10 Home/Multiple M.2 SSD Drives/T.Flight HOTAS X/HP Reverb G2
ED Team Solution BIGNEWY Posted Tuesday at 02:30 PM ED Team Solution Posted Tuesday at 02:30 PM Basic life cycle of a bug Bug is presented, We try to reproduce in public builds, If we reproduce we then check internal builds, Create an internal report with all data and tracks and which builds are affected, Dev will be assigned the task by a project manager, Fix is made, We test internally and merge if fixed or send back to dev, If fixed its merged, we test again once in closed testing, Closed testers will check also, then if fixed it will be in the patch notes for public patch day. Project managers decide the priority of bug reports, they have the full picture of what is involved and if the bug or report is tied to other issues or new features. Some issues can take much longer than others, it wont always be obvious to the end user why, but all the fixes we make will be in the change log. thanks 7 1 Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Recommended Posts