From 44ee849fafa9008aacd3b7263dcf9654ef53689f Mon Sep 17 00:00:00 2001 From: Oliver Hamlet Date: Sat, 9 Apr 2016 18:00:05 +0100 Subject: [PATCH] Update Making A Release page content --- docs/team/Making-A-Release.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/team/Making-A-Release.html b/docs/team/Making-A-Release.html index 261c3ff..da967af 100644 --- a/docs/team/Making-A-Release.html +++ b/docs/team/Making-A-Release.html @@ -3,7 +3,7 @@ layout: page title: Making A Release --- -

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

+

This page describes what needs to be done when releasing a new version of LOOT.

Preparation

@@ -16,12 +16,12 @@ title: Making A Release

Masterlists

+

Update the "update released" message version check in each masterlist's default branch. If the new release makes metadata syntax changes:

+
    -
  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. -
  6. Update the "update released" message version check in each masterlist's previous version branch.

Packaging

@@ -30,7 +30,7 @@ title: Making A Release
  • Build an x86 LOOT executable.
  • Build an x86 LOOT API DLL.
  • Run the installer script.
  • -
  • Run the archiver archive.
  • +
  • Run the archiver script.
  • Release!