Original patch has been part of staging for 3 months now which makes up the majority of this merge's duration, during which staging users have only reported games fixed and none bugged. Maybe a better approach to this merge would have been to marked the few tests that failed as todo to be resolved later vs combining the entire effort into 1 merge request which again, has become so bloated that gitlab struggles to load the comments anymore. I realize staging probably represents a more narrow user test pool overall but proably a higher proportionality of gamers for real world apps/games most relevant to the original patch so maybe it should have been merged despite a few extra test cases failing which seem much more edge case vs real world cases. Just throwing out suggestions to manage other future bloat problems. Some of the bloat is my fault for being new but most of the bloat seems only avoidable by more effective methods of splitting. If other devs are given more leniency for incremental iterative improvements via separate merge requests then please consider applying it for me as well so that the overall effort is more easily trackable/manageable. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/10567#note_148592