Page 1 of 3

Status of freeciv-3.0

Posted: Wed Feb 20, 2019 12:24 am
by cazfi
Freeciv-3.0 is approaching datafile format freeze milestone. Changes to ruleset and tileset formats have been minimal for some time already. If there's an issues with these, please let us know now before they are frozen and further changes need to wait for freeciv-3.1.
The d3f ticket is Task #656466.

Current freeciv-3.0 features relative to freeciv-2.6 are listed in http://www.cazfi.net/freeciv/FEATURES-3.0.txt

While development timeline of each version is unique, for reference: freeciv-2.6 d3f was at March 2016 and freeciv-2.6.0 was released July 2018.

I'm currently building a new Windows build from S3_0, expect it to be available in a couple of days.

Re: Status of freeciv-3.0

Posted: Thu Feb 21, 2019 6:29 am
by Ignatus
There are concerns for changes in the combat system to accompany the introduction of the rounds-limited combat. While the defender selection may be independent of datafiles (my draft on Wikia), the veteranship mechanism, if changed, probably should have settings associated.

Re: Status of freeciv-3.0

Posted: Thu Jun 13, 2019 11:20 pm
by cazfi
S3_0 datafile formats are in a sort of semi-freeze already. We don't expect formats to change any more (short of setting the final 3.0 capstrings), but as there's no hard freeze yet, we can still change them if something critical comes up. I'm planning version number bump to indicate all that (Feature #821608). New Windows builds will be made soon after. The formal d3f (with setting the capstrings) is currently planned to take place 05-Oct-19 (Task #656466)

Re: Status of freeciv-3.0

Posted: Fri Jun 14, 2019 3:44 am
by cazfi
cazfi wrote:New Windows builds will be made soon after.
Of course there's crosser-based nightly builds coming out every night when there has been changes to the codebase.
http://files.freeciv.org/packages/windo ... htly/S3_0/

Re: Status of freeciv-3.0

Posted: Sat Jun 22, 2019 10:28 am
by cazfi
cazfi wrote:I'm planning version number bump to indicate all that (Feature #821608).
Version number has now been bumped to 2.95.90. FEATURES-3.0.txt list of new features in 3.0 has been updated to match. New Windows build from S3_0 will be made within next couple of days (but there will be build from master finished first)

Re: Status of freeciv-3.0

Posted: Mon Jun 24, 2019 1:00 pm
by cazfi
cazfi wrote:S3_0 datafile formats are in a sort of semi-freeze already. We don't expect formats to change any more (short of setting the final 3.0 capstrings), but as there's no hard freeze yet, we can still change them if something critical comes up. I'm planning version number bump to indicate all that (Feature #821608). New Windows builds will be made soon after.
That Windows build is now available. See http://forum.freeciv.org/f/viewtopic.ph ... 2&start=21

Re: Status of freeciv-3.0

Posted: Thu Jun 27, 2019 5:49 am
by cazfi
cazfi wrote:That Windows build is now available.
I plan to make a quick (within a week from now) iteration on that. New build should have Bug #823431 fixed for you ruleup pleasure, and amplio2 and trident extra_units included.

Re: Status of freeciv-3.0

Posted: Sat Jun 29, 2019 1:42 pm
by cazfi
We may make such a ruleset format change that support for unit type flag "Coast" gets dropped from S3_0. The feature simply isn't ready yet, and we're not going to make 3.0 to wait for it any longer. (Bug #682425)

Re: Status of freeciv-3.0

Posted: Sun Jun 30, 2019 6:07 pm
by Ignatus
I think, the release should wait at least finishing 2.6.1 and playing some bigger 2.6 games. At least, we can put the feature out of standard rulesets and tell the AI not to use it but allow for mp gaming.

Re: Status of freeciv-3.0

Posted: Mon Jul 01, 2019 4:27 am
by cazfi
We've postponed S3_0 d3f by a couple of years already because 2.6 was so late. By October 2.6 has been out well over a year. It will probably take something like 2-3 years from d3f to 3.0.0 release (S2_6 d3f was 12-Mar-16, 2.6.0 release 21-Jul-18). Soon also 3.1 starts creating pressure (once upstreams release Qt6 and gtk4, we would need to get clients based on them out for modern distributions)