> Opinions welcome. I have a few ideas on the best way to approach this. - First of all, obviously, fix the WebGL CTS problems. (with --ignore-gpu-blacklist ) - Fix all other crashing issues and request re-inclusion. (This is comment #37.) Chrome versions are only 6 weeks, so not too bad of a lead time. - Set up fuzz testing to discover new crashing and stability issues before they impact userspace. This will also help with discovering the crash issues that need to get fixed. Chromium will probably loan ClusterFuzz resources to help with this. - Set up monkey testing with Chrome on Nouveau to discover the causes of the black-rectangle bugs. - Set up as-rendered diff testing between major Nouveau versions vs HEAD and require review of differences before a release can be made. (see https://fifoci.dolphin-emu.org/about/ for prior art) - Set up diff testing with the propietary NVIDIA drivers. (This may cost a significant amount of money to do.) All of this requires developer time and effort to do. You might need to organize a call for volunteers from a wider audience than just the nouveau mailing list. Best of luck, ~Kane _______________________________________________ Nouveau mailing list Nouveau@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/nouveau
