Difference between revisions of "Releasing Products"

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

Revision as of 22:05, 2 July 2022

Releasing SourceMod

  • 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/<new release folder>, 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 downloads.php.
  • Update ~sourcemod 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.<version> 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 script for the new version in ~sourcemod/update.
  • Change the ~sourcemod/compiler symlink to the new version.
  • Update hardcoded verison in ~sourcemod compiler.php.
  • git checkout new branch in ~sourcemod/sourcemod, then generate.py in /scripts/sourcepawn/exp/docgen/generate