Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
This release cycle already took too long, and some of the plans for Next+1 may again lead to a rather long and tricky test-bugfix-playtest-bugfix-playtest cycle.
Additionally, some of us devs suffer from both time constraints and mental/motivational exhaustion from the current release cycle, so the next few months are likely to remain slow in terms of progress on bleed.
The catch is that due to the amount of changes the current release cycle introduced, chances are rather high that even those playtests may not be enough to catch everything in time, plus there are already some PRs filed that, while too late/risky to be picked to prep this short before the planned release, still look like good candidates for a relatively quick follow-up release, due to either being bugfixes or having a (presumably) good "low risk, notable benefit" ratio.
This meta issue is meant as a place to collect those candidates until we make the call whether such a stop-gap release would make sense or we'd be better off moving on and just trying to keep Next+1 a bit more focused in scope and and amount of code changes.
Note: To keep scope and risks limited, only PRs that should be backwards-compatible with prep-1908 and are generally low-risk/easy-to-test should be included.
AI modding improvements: