Reply To cazfi
Maybe try to get it out relatively soon after d3f, and not to wait the usual 6 months between alphas?
My proposal for the plan would be getting alpha4 out relatively soon (for providing d3f version to wider audience), then alpha5 after npf (to provide npf version to wider audience), and then we hopefully are getting close to beta1 already so there wouldn't be need for alpha6.
3.1.0-alpha4 is commit cb3e87d4cd5592bf3a0501ca218deee79d7d54d2
I made a stupid mistake ending with commit message practically from alpha3, but in the tarball version number if correct.
Starting to plan release goals etc for S3_1-alpha4. Maybe try to get it out relatively soon after d3f, and not to wait the usual 6 months between alphas?
Blockers:
- NoHome unit homecity regression since alpha3: #45196 (done)
- Lua CVE-2022-33099: #45248 (done)
- installer_cross gtk4-client build fails from tarball: #45432 (done)
- meson build fails from tarball: #45433 (done), #45451 (done)
- Mitigate meson problems of detecting Qt6: #45446 (done)
- freeciv-manual regression since alpha3: #45508 (done)
- Translatability broken, translators can't use current build for working: #45518 (done)
High priority, but not strictly blockers:
- Support freeciv-3.1 features on a laptop without numpad: #44496 (done)
- Stealth units removal-from-client regression since 3.0: #45347 (done)