-
Notifications
You must be signed in to change notification settings - Fork 161
Release procedure
Al edited this page Aug 6, 2024
·
5 revisions
- Tutorials
- Notify translators on Discord that they can start translating.
- Notify theme authors if they need to update their themes.
- Also check the themes in the
modorganizer
repository.
- Also check the themes in the
-
Create a draft release on Github:
- Update
version.rc
inmodorganizer
anduibase
. Make sureFILEFLAGS
is(0)
, notVS_FF_PRERELEASE
. Commit and push. - Build the release (
mob -d somewhere release official master
). - Create a draft release on Github. Get other devs to test it to make sure everything's fine.
- Update
-
After other devs have approved the release, update documentation:
- Github: Update the What's New and Changelog wiki pages.
- Nexus: Update the News section in the main description.
- Nexus: Update the Logs tab (manage/documentation, add new changelog at the bottom).
-
Create the release on Nexus.
- Access the shared nexus account (credentials are shared between MO2 GitHub Org admins on Proton Pass).
- Releases should only be performed from this account (owner of the page) for security reasons, as the release files will otherwise be automatically quarantined.
- Upload the files, make sure to select the ones they're replacing.
- Either use the "update version" checkbox when uploading a file or make sure to change the version (manage/mod details).
- Wait for Nexus Antivirus check to pass and verify the files. If it fails contact Nexus community staff for manual clearance.
-
After the files are verified on Nexus, publish the draft release on Github.
-
Socials:
- Make a reddit post in r/skyrimmods.
- Post a message in #dev-builds pinging @ everyone with a link to the reddit post.
-
Branch all repos.