alain_bkr May i suggest to raise the Severity of those tickets to 9-Highest
Thus everyone will see what is critical, and put more efforts one these issues.
Reply To alain_bkr
May i suggest to raise the Severity of those tickets to 9-Highest
I've now elevated severity of most of them. We reserve 9 for "emergency fixes" (bypassing review periods etc), but anything above the default (5) shows up from the list. I've used just 6 for that, 7 for things with security implications.
3.0.2 tag pushed to github. S3_0 is now open for 3.0.3 development.
We have a lot of things that we *may* fix to 3.0.2, but let's track here what are the critical must things. I assume that 3.0.2 gets released at some point before my summer break.
- create_command_newcomer() bypassing server operator set restriction: #44185 (done)
- Lua vulnerability: #44467 (done)
- Update vulnerabilities reporting documentation (email address): #44479 (done)
- Unit orders cancelling regression since 3.0.1: #44504 (done)
- Unit orders cancelling regression since 3.0.1, part 2: #44519 (done)
- clang-15 build failures: #44563 (done), #44564 (done)
- License information in appdata files: #44712 (done)
- Build failure with gcc-12 & -O3: #44790 (done)