Release procedure - ModOrganizer2/modorganizer GitHub Wiki

Things to keep an eye on (most likely untested by beta-testers)

  • Tutorials

Before the first Release Candidate

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

For the release

  1. Create a draft release on Github:

    1. Update version.rc in modorganizer and uibase. Make sure FILEFLAGS is (0), not VS_FF_PRERELEASE. Commit and push.
    2. Build the release (mob -d somewhere release official master).
    3. Create a draft release on Github. Get other devs to test it to make sure everything's fine.

  2. After other devs have approved the release, update documentation:

    1. Github: Update the What's New and Changelog wiki pages.
    2. Nexus: Update the News section in the main description.
    3. Nexus: Update the Logs tab (manage/documentation, add new changelog at the bottom).

  3. Create the release on Nexus.

    1. Access the shared nexus account (credentials are shared between MO2 GitHub Org admins on Proton Pass).
    2. Releases should only be performed from this account (owner of the page) for security reasons, as the release files will otherwise be automatically quarantined.
    3. Upload the files, make sure to select the ones they're replacing.
    4. Either use the "update version" checkbox when uploading a file or make sure to change the version (manage/mod details).
    5. Wait for Nexus Antivirus check to pass and verify the files. If it fails contact Nexus community staff for manual clearance.

  4. After the files are verified on Nexus, publish the draft release on Github.

  5. Socials:

    1. Make a reddit post in r/skyrimmods.
    2. Post a message in #dev-builds pinging @ everyone with a link to the reddit post.

  6. Branch all repos.