S3_0 alpha1 testing
Posted: Tue Mar 13, 2018 5:39 pm
We are soon about to reach point that we will call alpha1 in S3_0 development. Current estimate of the date is Friday 16-Mar-18.
Alpha1 is not a full release, 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 alpha1 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).
I'm going to announce to this thread when ever new S3_0 alpha1 compatible components are made available. Some things I hope to achieve:
- Tarball of S3_0 alpha1 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)
- Setup public server of S3_0 for the first time to h1.jasminek.net (that is network compatible with all the alpha1 client builds despite S3_0 not having reached network protocol freeze yet)
- Make modpacks available with modpack installer compatible with alpha1, at least temporarily (until they are further updated as freeciv S3_0 development progress)
- Make 'Generic Build Scripts' (http://forum.freeciv.org/f/viewtopic.php?f=8&t=89944) able to build from S3_0 alpha1 tarball
Alpha1 is not a full release, 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 alpha1 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).
I'm going to announce to this thread when ever new S3_0 alpha1 compatible components are made available. Some things I hope to achieve:
- Tarball of S3_0 alpha1 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)
- Setup public server of S3_0 for the first time to h1.jasminek.net (that is network compatible with all the alpha1 client builds despite S3_0 not having reached network protocol freeze yet)
- Make modpacks available with modpack installer compatible with alpha1, at least temporarily (until they are further updated as freeciv S3_0 development progress)
- Make 'Generic Build Scripts' (http://forum.freeciv.org/f/viewtopic.php?f=8&t=89944) able to build from S3_0 alpha1 tarball