loot/loot.github.io
0
0
Fork 0
mirror of https://github.com/loot/loot.github.io.git synced 2026-07-27 14:13:30 -07:00
Code Issues Packages Projects Releases Wiki Activity
Page: Making A Release
Pages
Dirty Edits, Mod Cleaning & CRCs Error Reporting won't install Global Priorities Home How To Contribute How To Report Issues Helpfully Introduction To Load Orders LOOT FAQs Making A Release Masterlist Editing Masterlist Versioning Quickly Testing Your Masterlist Changes Resolving Conflicts Setting Windows' File Permissions Team Member Responsibilities Team Members Team Policies Thread Management Using Noto fonts for Chinese and Korean in LOOT
Clone
9
Making A Release
Oliver Hamlet edited this page 2015-09-27 13:06:33 +01:00
Table of Contents

What needs to be done to release a new version of LOOT.

Preparation

  1. Make sure that the release date and version history have been updated in the readme and src/api/api.h.
  2. Update the version numbers in src/api/api.h, src/backend/globals.cpp.in, src/resource.rc and scripts/installer.iss.
  3. Compile the .mo translation files from the .po files in the loot repository.
  4. Generate a new LaTeX copy of the API documentation, and from that generate a PDF.

Masterlists

  1. If the new release makes metadata syntax changes:
  2. For each masterlist, create a new version branch for that release.
  3. For each masterlist, set the default repository branch on GitHub to the new branch.
  4. Update the default masterlist branch settings for each game, in src/backend/game/game_settings.cpp and src/gui/loot_state.cpp.
  5. Update the "update released" message version check in each masterlist's previous version branch.

Packaging

  1. Build an x86 LOOT executable.
  2. Build an x86 LOOT API DLL.
  3. Run the installer script.
  4. Run the archiver archive.

Release!

  1. Create a release in GitHub's loot/loot repository and add installer and both archives (application and API) to it.
  2. Commit the release's documentation to an appropriate subfolder in the docs directory of LOOT's website repository, and update docs/index.html to list it.
  3. Post an announcement in the official forum thread.

General

Contributing

Team Stuff