Difference between revisions of "Releasing Products"

From AlliedModders Wiki
Jump to: navigation, search
m
Line 1: Line 1:
 
=Releasing SourceMod=
 
=Releasing SourceMod=
1. Create a git branch.
+
<li>Create a git branch.</li>
2. 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>
3. mount -orw /mnt/downloads on web01.
+
<li>mount -orw /mnt/downloads on web01.</li>
4. 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>
5. mount -oro /mnt/downloads.
+
<li>mount -oro /mnt/downloads.</li>
6. 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>
7. Update ~sourcemod downloads.php.
+
<li>Update ~sourcemod downloads.php.</li>
8. Update ~sourcemod vbcompiler.php.
+
<li>Update ~sourcemod vbcompiler.php.</li>
9. 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>
10. Create a compiler-1.<version> folder, drop spcomp + includes there.
+
<li>Create a compiler-1.<version> folder, drop spcomp + includes there.</li>
11. 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>
12. 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>
13. Add a script for the new version in ~sourcemod/update.
+
<li>Add a script for the new version in ~sourcemod/update.</li>
14. Change the ~sourcemod/compiler symlink to the new version.
+
<li>Change the ~sourcemod/compiler symlink to the new version.</li>

Revision as of 00:56, 19 October 2019

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 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.