S3_0 alpha2
Posted: Wed Oct 03, 2018 6:38 pm
We could make a new light-weight release alpha2 of S3_0 soon, if there's demand for one. So would anyone find such a thing useful?
At this point S3_0 datafile formats are getting close to their final form, but they are not frozen yet. In fact, one of the reasons to release alpha2 would be getting more testing of the current datafile formats in order to see what problems they may still have that should be addressed before they are frozen.
Alpha releases are not a full releases, but just a point of development where we do a lot of things with the same version control commit. In the usual development flow Windows build I make from the development HEAD today is from different commit than server setup I do with development HEAD of tomorrow. When both Windows build and server setup are made from the same alpha commit, they are compatible despite the fact that S3_0 has not yet reached neither datafile format freeze nor network protocol freeze (so things between two different commits are not guaranteed to be compatible).
Some things I would hope to achieve with alpha2:
- Tarball of S3_0 alpha2 to test building from
- Windows builds with msys2. In S3_0, msys2 is made the default Windows build environment, and msys1 isn't even available any more (it can't be used to build freeciv S3_0)
- Windows builds with crosser setup (installer_cross)
- Make modpacks available with modpack installer compatible with alpha2, at least temporarily (until they are further updated as freeciv S3_0 development progress)
- Make 'Generic Build Scripts' (viewtopic.php?f=8&t=89944) able to build from S3_0 alpha2 tarball
At this point S3_0 datafile formats are getting close to their final form, but they are not frozen yet. In fact, one of the reasons to release alpha2 would be getting more testing of the current datafile formats in order to see what problems they may still have that should be addressed before they are frozen.
Alpha releases are not a full releases, but just a point of development where we do a lot of things with the same version control commit. In the usual development flow Windows build I make from the development HEAD today is from different commit than server setup I do with development HEAD of tomorrow. When both Windows build and server setup are made from the same alpha commit, they are compatible despite the fact that S3_0 has not yet reached neither datafile format freeze nor network protocol freeze (so things between two different commits are not guaranteed to be compatible).
Some things I would hope to achieve with alpha2:
- Tarball of S3_0 alpha2 to test building from
- Windows builds with msys2. In S3_0, msys2 is made the default Windows build environment, and msys1 isn't even available any more (it can't be used to build freeciv S3_0)
- Windows builds with crosser setup (installer_cross)
- Make modpacks available with modpack installer compatible with alpha2, at least temporarily (until they are further updated as freeciv S3_0 development progress)
- Make 'Generic Build Scripts' (viewtopic.php?f=8&t=89944) able to build from S3_0 alpha2 tarball