Difference between revisions of "Releasing Products"

From AlliedModders Wiki
Jump to: navigation, search
m (wiki markup instead of HTML)
(update instructions)
Line 1: Line 1:
 
== Releasing SourceMod ==
 
== Releasing SourceMod ==
* Create a git branch.
+
 
* Update master.cfg in buildbot buildmaster. Don't forget to push the change to github.
+
'''''Bold italic''''' values should be replaced as appropriate for the release.
* mount -orw /mnt/downloads on web01.
+
 
* mkdir /mnt/downloads/smdrop/<new release folder>, chmod 775 it, fix ownership.
+
* Create a git branch
* mount -oro /mnt/downloads.
+
* Update master.cfg in buildbot buildmaster. Don't forget to push the change to github
* Fix sm_commit_log by updating last ~N master builds to be the new stable branch.
+
* mount -orw /mnt/downloads on web01
* Update ~sourcemod downloads.php.
+
* mkdir /mnt/downloads/smdrop/'''''1.11''''', chmod 775 it, fix ownership
* Update ~sourcemod vbcompiler.php.
+
* mount -oro /mnt/downloads
* Update forums newpost.php and editpost.php (search for ccversion). Do this on staging, create a production PR in bitbucket, then pull.
+
* Fix sm_commit_log by updating last ~N master builds to be the new stable branch
* Create a ~sourcemod/compiler-1.<version> folder, drop spcomp + includes there.
+
* Update ~sourcemod/public_html/downloads.php
* Add an entry to web-commit-updater/updater.php for the new version.
+
* Update ~sourcemod/public_html/vbcompiler.php
* Force builds on the new dev and stable branches via pushbuild.txt.
+
* Update forums newpost.php and editpost.php (search for ccversion). Do this on staging, create a production PR in bitbucket, then pull
* Add a script for the new version in ~sourcemod/update.
+
* Create a ~sourcemod/'''''compiler-1.11''''' folder, drop spcomp + includes there
* Change the ~sourcemod/compiler symlink to the new version.
+
* Add an entry to web-commit-updater/updater.php for the new version
* Update hardcoded verison in ~sourcemod compiler.php.
+
* Force builds on the new dev and stable branches via pushbuild.txt
 +
* Add a ~sourcemod/update/'''''update-1.11.sh''''' script for the new version
 +
* Clone the new branch into ~sourcemod/update/'''''1.11-dev'''''
 +
* Run ~sourcemod/update_addversion.php --version '''''1.11''''' --path '''''1.11-dev''''' (with appropriate values)
 +
* Change the ~sourcemod/compiler symlink to the new version
 +
* Update hardcoded verison in ~sourcemod/public_html/compiler.php.
 
* git checkout new branch in ~sourcemod/sourcemod, then generate.py in /scripts/sourcepawn/exp/docgen/generate
 
* git checkout new branch in ~sourcemod/sourcemod, then generate.py in /scripts/sourcepawn/exp/docgen/generate

Revision as of 22:14, 2 July 2022

Releasing SourceMod

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

  • Create a git branch
  • Update master.cfg in buildbot buildmaster. Don't forget to push the change to github
  • 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
  • Update ~sourcemod/public_html/vbcompiler.php
  • Update forums newpost.php and editpost.php (search for ccversion). Do this on staging, create a production PR in bitbucket, then pull
  • Create a ~sourcemod/compiler-1.11 folder, drop spcomp + includes there
  • Add an entry to web-commit-updater/updater.php for the new version
  • Force builds on the new dev and stable branches via pushbuild.txt
  • Add a ~sourcemod/update/update-1.11.sh script for the new version
  • Clone the new branch into ~sourcemod/update/1.11-dev
  • Run ~sourcemod/update_addversion.php --version 1.11 --path 1.11-dev (with appropriate values)
  • Change the ~sourcemod/compiler symlink to the new version
  • Update hardcoded verison in ~sourcemod/public_html/compiler.php.
  • git checkout new branch in ~sourcemod/sourcemod, then generate.py in /scripts/sourcepawn/exp/docgen/generate