Topic: Release 1.3

Nordfriese
Avatar
Topic Opener
Joined: 2017-01-17, 18:07 UTC+1.0
Posts: 2193
OS: Debian Testing
Version: Latest master
Ranking
One Elder of Players
Location: 0x55555d3a34c0
Posted at: 2025-05-31, 20:28 UTC+2.0

This is a the thread for everything pertaining to the upcoming release of version 1.3. As with 1.2, we are somewhat behind the intended one-year release cadence, but again we have some great new features to show for it.

I have marked some of the open issues and PRs as urgent and postponed the rest. The distinction is in several cases arbitrary, there are a number of goodies that I'd like to see in v1.3 if possible but that are not critical and might not make it; and some of the other open PRs can still be merged for v1.3 if we get a more timely response. As always, discuss if you disagree with any categorisations.
Notably, I have postponed the many outstanding balancing changes due to lack of consensus. Naval warfare will not come out of its preview status in 1.3 yet since there were no major changes that received both sufficient attention and consensus.

I want to call the first snow feature freeze for Widelands 1.3 to take place one month from now on Tuesday, July 1st, 2025, at 00:00 CEST.

As in previous release cycles, new features labelled Urgent can still be merged after the freeze. When all remaining urgent issues are fixed, we can schedule the winter time freeze and the release dates.


Top Quote
tothxa
Avatar
Joined: 2021-03-24, 12:44 UTC+1.0
Posts: 547
OS: antiX / Debian
Version: some new PR I'm testing
Ranking
One Elder of Players
Posted at: 2025-05-31, 21:45 UTC+2.0

Naval warfare will not come out of its preview status in 1.3 yet since there were no major changes that received both sufficient attention and consensus.

I'm very disappointed that we didn't get any progress on the warship spamming issue, and even the discussion stopped. face-sad.png On my part the reason was that reviews in this cycle were very slow, so I didn't want to start more new PRs, even though I had many ideas I wanted to work on...


Top Quote
hessenfarmer
Avatar
Joined: 2014-12-11, 23:16 UTC+1.0
Posts: 2878
Version: always the latest
Ranking
One Elder of Players
Location: Bavaria
Posted at: 2025-10-16, 22:05 UTC+2.0

As we do claim to support only supported OS Versions, and windows 10 fell out of official support 2 days ago, there is no supported 32 Bit windows version available any more.
Mingw is skipping support for 32 Bit slowly since a couple of years as well, so it might be the time to stop our 32 Bit builds.
Maybe we might build 1.3 one last time as win 10 has extended security support for one more year. But aterwards we should stop it imho.


Top Quote
Nordfriese
Avatar
Topic Opener
Joined: 2017-01-17, 18:07 UTC+1.0
Posts: 2193
OS: Debian Testing
Version: Latest master
Ranking
One Elder of Players
Location: 0x55555d3a34c0
Posted at: 2025-10-17, 19:28 UTC+2.0

Good point. However my stance on compatibility in automated builds is usually that configurations we no longer officially support can just run on for as long as they still keep working, as it doesn't cost us anything to keep providing these builds, and only drop them when they stop to work smoothly. Although given that the windows build system needs changes every now and then after some dependency updates I expect this might not be very long actually face-wink.png


Top Quote
hessenfarmer
Avatar
Joined: 2014-12-11, 23:16 UTC+1.0
Posts: 2878
Version: always the latest
Ranking
One Elder of Players
Location: Bavaria
Posted at: Yesterday 15:04 UTC+1.0

while checking on github I realized that macOS 13 has fallen out of support in september as well, and is already deprecated on github with the final end date of december the 4th.
Github has introduced a macos 15 intel runner to have an OSS compatible Intel runner, but they announced it will be the last of the intel architecture.

I will add the macos 15 intel runner to our config. But as Apple users tend to use their hardware very long as well, my suggestion would be to leave the macos 13 image in as long as possible in case we get the release before december 4th, to provide a last time macos 13 version.


Top Quote
Ron_of_Nord
Avatar
Joined: 2024-04-20, 23:43 UTC+2.0
Posts: 201
OS: Windows
Version: 1.3
Ranking
Widelands-Forum-Junkie
Location: Land_down_under
Posted at: Today 06:57 UTC+1.0

Hi just a quick question on this, are you planning on stopping Windows 10 64-bit support?
I ask simply because my laptop is a 64 bit machine running windows 10 ( I don't plan on upgrading OS or Hardware
till after christmas ) If this is the case, is version 1.3 the final version for this level of system ?
Thanks in advance.


The aussies are coming, ya ho! ya ho!

Top Quote
hessenfarmer
Avatar
Joined: 2014-12-11, 23:16 UTC+1.0
Posts: 2878
Version: always the latest
Ranking
One Elder of Players
Location: Bavaria
Posted at: Today 10:10 UTC+1.0

Our Windows 64 bit builds should continue to run on Windows 10, as there is no external dependency to OS provided data or functions, as our builds are static builds with all needed packages included.
Therefore for our game it does not matter if you run it on Windows 11 or Windows 10.
However if specific issues will arise on Win10 which won't be reproducable on Win11 we can't provide any support any longer, but the probability for this is currently extremely low. Reason is that me and most probably the other Windows devs have upgraded our machines to Win 11 already, for security reasons and so we do not have any testing environment for Win10 anymore.

so to keep it short, most probably widelands Versions after 1.3 will still run on Win10 64bit (as well as on Win7 64bit), although not official supported anymore.


Top Quote