Skip to content

ReleaseProcess.md

Latest commit

 

History

History
31 lines (29 loc) · 2.41 KB

ReleaseProcess.md

File metadata and controls

31 lines (29 loc) · 2.41 KB
Raw

Release Process

Rough notes on the steps we follow when making an SML release.

  1. Add things demonstrating/testing new features to Example Mod and SMLFeatureTests when relevant
  2. Ensure docs repository is updated (on https://docs-dev.ficsit.app/, at least)
  3. Write version-specific Updating Guide on the docs when relevant
  4. Write draft release changelog on GitHub, following the format from the previous release
  5. Ensure SML VS project and mod compiles on a developer machine
  6. Ensure the CI passes on the dev branch
  7. Open a SML PR of dev to master and get approvals
  8. Update the docs versions
    1. Create branch for old version
    2. Commit on old version branch: Set version number for version branch. Point to archived download links for SML and engine
    3. Commit on main (or dev to go into main) branch: add old version branch as another branch to build
  9. After merging the PR, commit on master a Bump version commit
    • SML.uplugin GameVersion and SemVersion
    • ExampleMod.uplugin GameVersion and SML dependency version
  10. Wait for CI to finish. We don't upload locally compiled versions so the version detailed suffix is consistent across versions. We want the CI result of the commit on master, so cancel the CI runs for the dev that probably started when those were pushed to save time.
  11. While waiting for CI to finish:
    1. Merge the docs PR to master
    2. Update SMLFeatureTests SML dependency version
  12. Upload files to the draft GitHub release. Attach all of the CI zip file contents as release items (Windows (Client), Windows Server, Linux Server, SML (multi-target))
  13. Attach CI artifact to SMR as a new version of the SML mod (multi-target zip file), SMR changelog is the GitHub changelog
  14. Upload the ficsit.app version, and once virus scan succeeds, publish the GitHub draft release
  15. Post in #toolkit-updates and/or #announcements on Discord
  16. Clear/create ficsit.app announcements as needed via site admin announcements panel