The observant will have noticed that it's no longer June and 2.6.0 was
not yet released. However, we did get RC1 out.
My plan is:
- If no showstopping bugs appear, release 2.6.0-final on the weekend of
14-15 July. (Marko points out that this gives Windows users a weekend
with RC1.)
- However, if something important enough shows up in the next day or
two, I can make an RC2 on 7-8 July.
- In the meantime, strings are frozen, to give translators a chance to
catch up. They'll be unfrozen after 2.6.0. *
- Per <http://www.freeciv.org/wiki/Release#Release_Candidate>,
code changes othe than to fix critical bugs are also discouraged, to
reduce the risk of last-minute slip-ups.
Once 2.6.0 is final I expect it'll be going into Debian/Ubuntu, and I
think there's a decent chance that Ubuntu Cosmic will ship with 2.6.0
rather than any later version, so it would be a shame if we
introduced a last-minute regression.
* However, translators should note that an unmarked string was found:
<https://www.hostedredmine.com/issues/763068>
That'll show up as untranslated/fuzzy before 2.6.0. I've already
uploaded updated po-files for S2_6 on the assumption that the patch will
go through: <http://files.freeciv.org/translations/S2_6/>
As Marko says, translation updates are still very welcome.
There are still issues with 2.6 that I'd like to address, but I don't
think it's worth holding up 2.6.0 any longer for them.
<http://www.freeciv.org/wiki/NEWS-2.6.0-RC1#Known_issues_in_2.6> lists
what I think are the most important ones.
I expect there'll be one more 2.5 release at some point, to mop up the
bugfixes already on that branch for the benefit of Longturn players etc.
Doesn't seem like enough yet to be worth making it at the same time as
2.6.0 though.
