forked from scp-fs2open/fs2open.github.com
-
Notifications
You must be signed in to change notification settings - Fork 0
New release procedure
m!m edited this page Aug 26, 2015
·
1 revision
To help streamline how a new release would be handled here is a small list with the necessary steps:
- Create a forum post saying that we plan on a new release soon which contains a call for modders and users to bring breaking bugs or critical missing features to our attention so those can be fixed or added before the release. Features would only be added for mods that are close to completion.
- Once those issues have been resolved (or none have been reported) we begin by creating a release branch based on master and add a RC-1 tag for that commit. Based on that commit the first release candidate build is compiled.
- If bugs are found those are fixed and a new RC tag is created and new builds are posted. GOTO 3.
- If no bugs are reported the current release candidate will be relabeled as the final release and that commit is tagged as the release version.