Releasing Products

From AlliedModders Wiki
Revision as of 07:40, 24 July 2022 by Fyren (talk | contribs)
Jump to: navigation, search

Releasing SourceMod

Bold italic values should be replaced as appropriate for the release.

  • General
    • Create a git branch
    • Bump sourcemod/plugins/include/version.inc numbers for manual builds
  • Buildbot
    • Update master.cfg in buildbot buildmaster. Don't forget to push the change to github
    • Force builds on the new dev and stable branches via pushbuild.txt
  • Downloads
    • mount -orw /mnt/downloads on web01
    • mkdir /mnt/downloads/smdrop/1.11, chmod 775 it, fix ownership
    • mount -oro /mnt/downloads
    • Fix sm_commit_log by updating last ~N master builds to be the new stable branch
    • Update ~sourcemod/public_html/downloads.php
    • Add an entry to web-commit-updater/updater.php for the new version
  • Gamedata updater
    • Clone the new branch into ~sourcemod/update/1.11-dev
    • Add a ~sourcemod/update/update-1.11.sh script for the new version
    • Run ~sourcemod/update/add_version.php --version 1.11.0 --path 1.11-dev
    • Run ~sourcemod/update/add_version.php --version 1.12.0 --path master
  • Web compiler and forum
    • Create a ~sourcemod/compiler-1.11 folder, drop spcomp + includes there
    • Change the ~sourcemod/compiler symlink to the new version
    • Update hardcoded version in ~sourcemod/public_html/compiler.php and change the "you can use this to compile plugins for SourceMod 1.11 or higher" text if necessary
    • Update ~sourcemod/public_html/vbcompiler.php
    • Update forums newthread.php and editpost.php (search for ccversion). Do this on staging, create a production PR in bitbucket, then pull
  • SP docs
    • Rebuild ~sourcemod/scripts/sourcepawn/exp/tools/docparse if needed
    • git checkout new branch in ~sourcemod/scripts/sourcemod, then run generate.py in ~sourcemod/scripts/sourcepawn/exp/docgen/generate