Pre release testing Checklist, and release engine checklist

Pre-release testing

0. Build and release an engine (release is needed so that cluster can easily grab engine)
1. Sync test vs headless on linux with a few barbarian AIs, on a mixed mode map such as Pentos.

• Choose a cluster, and update the engine by grabbing the url of the linux build from the releases page (so that wget can download it)
• In the cluster, run ~/spads/spads_config_bar/python3 spads_config_bar_updater.py -u [engine url from github]
• Edit ~/spads/etc/latest_engine_spads.conf springServer and unitsyncDir parameters

2. Check Chobby, and restarting a skirmish from chobby. To do this, you need to have the following:

• BYAR-Chobby.sdd and Chobby.sdd checked out into your /data/games folder
• empty devmode.txt in /data
• A config-dev.json file in /data, which points to the engine version that you want to test:

{
    "title" : "Beyond All Reason",
    "setups" : [
        {
            "package": {
                "id": "dev-lobby",
                "display": "Dev Lobby"
            },
            "downloads": {
                "engines" : [ "105.1.1-691-g9295c10 BAR105" ]
            },
            "no_start_script" : true,
            "no_downloads" : true,
            "auto_start": true,
            "launch": {
                "start_args" : ["--menu", "BYAR Chobby $VERSION"]
            }
        }
    ]
}

• Make sure to place the engine to test in /data/engine/[exact folder name in config-dev.json]
• A command line shortcut to your beyond all reason launcher, which will launch chobby in devmode with the new engine: C:\Users\*\AppData\Local\Programs\Beyond-All-Reason\Beyond-All-Reason.exe -c C:\Users\*\AppData\Local\Programs\Beyond-All-Reason\data\config-dev.json

3. Test starting skirmish
4. Test saving skirmish
5. Test loading skirmish
6. Sync test online in engine testing autohost (usually engine testing 14)
7. Test that barbarians actually do things

On release

1. Update all clusters by shutting down cluster managers
2. Updating their engine and configs with:

• ~/spads/spads_config_bar/python3 spads_config_bar_updater.py -c -u [engine url from github]

3. Restart AU, US, EU and EU1 clusters
4. Update debug symbols for engine on stacktrace translator

• python update_debug_symbols.py [windows debug symbol.tgz url]

5. Update chobby config-dist.json to use correct engine as in https://github.com/beyond-all-reason/BYAR-Chobby/blob/master/README.md#how-to-make-new-launcher-releases
6. Wait for the update to build, then publish the draft release
7. Post links to new installers in #website