Ticket #44202

S3_1-alpha3

Open Date: 2022-03-27 05:39 Last Update: 2022-05-13 20:33

Reporter:
Owner:
Type:
Status:
Closed
Component:
MileStone:
(None)
Priority:
5 - Medium
Severity:
5 - Medium
Resolution:
Fixed
File:
None

Details

There's obviously the datafile formats point in S3_1-alpha3, but there's also other things that could be release goals. For some time, I've worked focusing to S3_1-alpha3 as a whole, not only the d3f part of it.

One big open question with S3_1-alpha3 is when we are about to release it, in relation to d3f. The main options are to release immediately after d3f, so that people could use it to start developing and testing 3.1 modpacks, or to release as soon as we semi-freeze the formats, meaning that we expect the only remaining change to be setting capstrs to their frozen form but can still fix things if something critical comes up. The latter option would mean that alpha3 using people could participate in that testing.

---

- Unit orders cancelling regression since 3.0.1: #44504 (done)
- Unit orders cancelling regression since 3.0.1, part 2: #44519 (done)
- Update vulnerabilities reporting documentation (email address): #44479 (done)
- Cannot enter huts with goto: #42133 (done)
- Compile failure with latest Qt6: #44514 (done)
- stub.serv not part of the tarball: #44555 (done)

Ticket History (3/15 Histories)

2022-03-27 05:39 Updated by: cazfi
  • New Ticket "S3_1-alpha3" created
2022-04-03 23:57 Updated by: alienvalkyrie
Comment

I'd go with the latter option, i.e. put out the alpha when we expect no more actual format changes (but before the actual freeze)

2022-04-12 11:30 Updated by: cazfi
Comment

Reply To alienvalkyrie

I'd go with the latter option, i.e. put out the alpha when we expect no more actual format changes (but before the actual freeze)

Let's aim to that.

2022-05-04 00:11 Updated by: cazfi
  • Details Updated
2022-05-05 00:42 Updated by: cazfi
Comment

All the modpacks available from the default modpack.list should now be updated to compatibility with S3_1 HEAD (-> which means alpha3 compatibility)

2022-05-05 00:55 Updated by: cazfi
Comment

Client crash #44511 affecting both of the custom ruleset modpacks from default modpack.list, it's sort of big issue for alpha3. Not sure about blocking alpha3 because of it, as it might take some time before there's a fix, and postponing alpha3 too much would make it pointless as the the version to test with, before the freeze.

2022-05-05 14:19 Updated by: cazfi
Comment

Reply To cazfi

Client crash #44511

Freeciv engine part of this was de-escalated to a need to implement ruleset load time sanity check against the kind of error those rulesets had.

2022-05-05 16:00 Updated by: cazfi
  • Details Updated
2022-05-06 11:48 Updated by: cazfi
Comment

Status of S3_1-d3f / S3_1-alpha2 on freeciv-dev: https://www.freelists.org/post/freeciv-dev/S3-1d3f

2022-05-06 20:15 Updated by: cazfi
  • Details Updated
2022-05-10 10:14 Updated by: cazfi
  • Details Updated
2022-05-12 08:39 Updated by: cazfi
  • Details Updated
2022-05-13 11:21 Updated by: cazfi
  • Owner Update from (None) to cazfi
  • Details Updated
2022-05-13 12:21 Updated by: cazfi
Comment

S3_1-alpha3 light-weight-release is commit 77852fdf347ffceab8e24f32e0a09b208458d73d

2022-05-13 20:33 Updated by: cazfi
  • Status Update from Open to Closed
  • Resolution Update from None to Fixed

Attachment File List

No attachments

Edit

You are not logged in. I you are not logged in, your comment will be treated as an anonymous post. » Login