As it seems that 2.6.3 will not be released soon, I'm planning to make
an emergency style 220.127.116.11 release with critical fixes accumulated
since 2.6.2 release. The plan is to create a new S2_6_2 branch from
S2_6 from the 2.6.2 release point, cherry-pick some fixes from S2_6
there, and to release 18.104.22.168 from that branch.
Fixes falling to following categories will be included:
- Critical build failures. Compiler warnings are not considered
critical, so -Werror/--enable-debug builds are still expected to fail
in some cases
- Crash bugs
- All documentation fixes, as they have really minimal risk of breaking anything
About the translation arrangements I'll send a new email (only to
freeciv-i18n) once I have the branch in place. There might be some
string changes relative to 2.6.2 release included
as part of the documentation changes. I'm aware of the fact that there
has been translation updates to S2_6 after 2.6.2 release that would
have been relevant for 2.6.2.
At the moment I expect release to be called 22.214.171.124, but if that
four-part versioning scheme turns out not to work as we test this, we
may end up calling it 2.6.3 in the end and to bump S2_6 to really be
about 2.6.4 development already. We have implemented four-part
versioning support to S2_6, but this would be the first time it's ever
I'll be working on this as time permits, but I may be able to release
as soon as in two to three weeks.