Difference between revisions of "Releasing Products"

From AlliedModders Wiki
Jump to: navigation, search
(update instructions)
m (Add product.version to files needing bumpage)
 
(10 intermediate revisions by one other user not shown)
Line 2: Line 2:
  
 
'''''Bold italic''''' values should be replaced as appropriate for the release.
 
'''''Bold italic''''' values should be replaced as appropriate for the release.
−
 
+
* General
−
* Create a git branch
+
** Create a git branch
−
* Update master.cfg in buildbot buildmaster. Don't forget to push the change to github
+
** Bump product.version and plugins/include/version.inc numbers for manual builds
−
* mount -orw /mnt/downloads on web01
+
* Buildbot
−
* mkdir /mnt/downloads/smdrop/'''''1.11''''', chmod 775 it, fix ownership
+
** Update master.cfg in buildbot buildmaster. Don't forget to push the change to github
−
* mount -oro /mnt/downloads
+
** Force builds on the new dev and stable branches via pushbuild.txt
−
* Fix sm_commit_log by updating last ~N master builds to be the new stable branch
+
* Downloads
−
* Update ~sourcemod/public_html/downloads.php
+
** Run <code>mount -orw /mnt/downloads</code> on web01
−
* Update ~sourcemod/public_html/vbcompiler.php
+
** Run <code>mkdir /mnt/downloads/smdrop/'''''1.11'''''</code>, chmod 775 it, fix ownership
−
* Update forums newpost.php and editpost.php (search for ccversion). Do this on staging, create a production PR in bitbucket, then pull
+
** Run <code>mount -oro /mnt/downloads</code>
−
* Create a ~sourcemod/'''''compiler-1.11''''' folder, drop spcomp + includes there
+
** Fix sm_commit_log by updating last ~N master builds to be the new stable branch
−
* Add an entry to web-commit-updater/updater.php for the new version
+
** Update <code>~sourcemod/public_html/downloads.php</code>
−
* Force builds on the new dev and stable branches via pushbuild.txt
+
** Add an entry to <code>~sourcemod/web-commit-updater/updater.php</code> for the new version
−
* Add a ~sourcemod/update/'''''update-1.11.sh''''' script for the new version
+
* Gamedata updater (run commands from inside <code>~sourcemod/update</code>)
−
* Clone the new branch into ~sourcemod/update/'''''1.11-dev'''''
+
** Clone the new branch into <code>'''''1.11-dev'''''</code>
−
* Run ~sourcemod/update_addversion.php --version '''''1.11''''' --path '''''1.11-dev''''' (with appropriate values)
+
** Create a <code>'''''update-1.11.sh'''''</code> script for the new version
−
* Change the ~sourcemod/compiler symlink to the new version
+
** Run <code>php add_version.php --version '''''1.11.0''''' --path '''''1.11-dev'''''</code>
−
* Update hardcoded verison in ~sourcemod/public_html/compiler.php.
+
** Run <code>php update/add_version.php --version '''''1.12.0''''' --path master</code>
−
* git checkout new branch in ~sourcemod/sourcemod, then generate.py in /scripts/sourcepawn/exp/docgen/generate
+
** Run <code>./'''''update-1.11.sh'''''</code>
 +
** Run <code>./update-master.sh</code>
 +
* Web compiler and forum
 +
** Create a <code>~sourcemod/'''''compiler-1.11'''''</code> directory, drop spcomp + includes there
 +
** Change the <code>~sourcemod/compiler</code> symlink to the new version
 +
** Update hardcoded version in <code>~sourcemod/public_html/compiler.php</code> and change the "you can use this to compile plugins for SourceMod '''''1.11''''' or higher" text if necessary
 +
** Update <code>~sourcemod/public_html/vbcompiler.php</code>
 +
** Update forum's newthread.php and editpost.php (search for ccversion). Do this on staging, create a production PR in bitbucket, then pull
 +
* SP docs
 +
** Pull and rebuild <code>~sourcemod/scripts/sourcepawn/exp/tools/docparse</code> if needed
 +
** <code>git checkout</code> new branch into <code>~sourcemod/scripts/sourcemod</code>
 +
** From <code>~sourcemod/scripts/sourcepawn/exp/docgen/generate/</code>, run <code>python generate.py</code>

Latest revision as of 10:58, 20 October 2024

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
  • 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
  • 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
  • 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/, run python generate.py
Retrieved from "https://wiki.alliedmods.net/index.php?title=Releasing_Products&oldid=11728"