Backwards compatibility issues people are reporting with the pygame 2 dev releases.
To try and focus we will have a feature freeze. Please no new features(or even fixes) that aren't related to these "critical" labeled issues stopping pygame 2 from being released.
If you want to do other things, please work on a separate fork (or branch if that's not suitable). Then after the two months we can look at merging them.
PRs are open for the next week(Sunday 24th November) if anyone really wants to merge something anyway.
other PRs will be closed until after the two months when we can consider them for merging again.
I will PIN one issue at a time to the github issues pages, and put a link to that one issue on the pygame website. When that one issue is fixed I'll put another one-issue on there. Repeating this one issue at a time until the two months are up, or we're done.
For all the critical issues I will go through and make a todo checklist in them of work that is remaining to be done.
minimal working example to reproduce the issue
write unit test(s)
point to which source function the issue is likely in.
other steps in a plan to fix the issue (example: maybe a function needs cleaning up first)