Releasing Products
Releasing SourceMod
Bold italic values should be replaced as appropriate for the release.
- General
- Create a git branch
- Bump product.version and 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
- Run
mount -orw /mnt/downloads
on web01 - Run
mkdir /mnt/downloads/smdrop/1.11
, chmod 775 it, fix ownership - Run
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
~sourcemod/web-commit-updater/updater.php
for the new version
- Run
- Gamedata updater (run commands from inside
~sourcemod/update
)- Clone the new branch into
1.11-dev
- Create a
update-1.11.sh
script for the new version - Run
php add_version.php --version 1.11.0 --path 1.11-dev
- Run
php update/add_version.php --version 1.12.0 --path master
- Run
./update-1.11.sh
- Run
./update-master.sh
- Clone the new branch into
- Web compiler and forum
- Create a
~sourcemod/compiler-1.11
directory, 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 forum's newthread.php and editpost.php (search for ccversion). Do this on staging, create a production PR in bitbucket, then pull
- Create a
- SP docs
- Pull and rebuild
~sourcemod/scripts/sourcepawn/exp/tools/docparse
if needed git checkout
new branch into~sourcemod/scripts/sourcemod
- From
~sourcemod/scripts/sourcepawn/exp/docgen/generate/
, runpython generate.py
- Pull and rebuild