Topic: Release 1.3
Nordfriese
Topic Opener
Joined:
2017-01-17, 18:07 UTC+1.0
Posts: 2193 OS: Debian Testing Version: Latest master  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. 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
Joined:
2021-03-24, 12:44 UTC+1.0
Posts: 547 OS: antiX / Debian Version: some new PR I'm testing One Elder of Players |
Posted at:
2025-05-31, 21:45 UTC+2.0
I'm very disappointed that we didn't get any progress on the warship spamming issue, and even the discussion stopped.
Top
Quote
|
|
hessenfarmer
Joined:
2014-12-11, 23:16 UTC+1.0
Posts: 2877 Version: always the latest 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.
Top
Quote
|
|
Nordfriese
Topic Opener
Joined:
2017-01-17, 18:07 UTC+1.0
Posts: 2193 OS: Debian Testing Version: Latest master 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
Top
Quote
|
|
hessenfarmer
Joined:
2014-12-11, 23:16 UTC+1.0
Posts: 2877 Version: always the latest One Elder of Players Location: Bavaria |
Posted at:
Today 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. 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
|
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...