This release-checklist.txt for version 1.5.3 is shortened in comparison to the one for ther release of 1.5.2 because the list of changes is smaller, contained to bugfixes only and only the core app is affected. 1. Zalewa ========= Most of these actions are non-destructive. They don't overwrite anything yet. Either they happen in the repos or only add new files. - Bump versions: Doomseeker in src/core/versiondefs.cmake - Update the [Unreleased] to the Doomseeker [version] in CHANGELOG.md - Add the ref link at the bottom of CHANGELOG.md to [version] - Verify the build on Windows and Linux - Commit all of these, then push. - Optional: if last-minute fixes need to be done, there is still time to do them before the tag is pushed - Tag version in the repo - Push the tag - Website: update Doomseeker version in download.php - Website: update version in the windows.zip filename in download_plugin.php - Website: set latest Doomseeker version in ind.php - Push the website to the repo - Package the "beta" channel update for Windows - DESTRUCTIVE: Deploy the update packages on the "beta" channel (updates/ dir) - Package the "stable" channel update for Windows - Copy the JSON meta file to a file named after the Doomseeker version tag: update-info_win32_stable_.js - DESTRUCTIVE: Deploy the update packages on the "stable" channel (updates/ dir) (it's okay to overwrite update-info_win32_stable.js at this point) - Package doomseeker-_windows.zip - Deploy doomseeker-_windows.zip on the website (files/ dir) - Deploy doomseeker-_windows.zip on the drdteam site 2. Blzut3 ========= - Build packages without dependency scanning, making sure to run cpackpostprocess.sh. - Install new libwadseeker on build system. - Rebuild packages with dependency scanning and deploy to repository. - Release Ubuntu & Mac binary packages - Package the source into a signed ".tar.xz" - Upload the source ".tar.xz" to (files/ dir) 3. Zalewa ========= - Deploy the website from the repo to the server - Forums announcement