From 33ae4be98e645b0b59596aa6e10e8ea1ad98a032 Mon Sep 17 00:00:00 2001 From: Oliver Hamlet Date: Sat, 22 Oct 2016 11:40:24 +0100 Subject: [PATCH] Update the making a release instructions --- docs/team/Making-A-Release.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/team/Making-A-Release.html b/docs/team/Making-A-Release.html index c110d92..92989d7 100644 --- a/docs/team/Making-A-Release.html +++ b/docs/team/Making-A-Release.html @@ -12,8 +12,8 @@ title: Making A Release

If the new release makes metadata syntax changes:

    -
  1. Run lomad using lomad -t <github personal access token> -a -b <branch name> to (for all masterlists) create a branch for that release and make it the default.
    2. -
  2. Update the default masterlist branch settings for each game in src/backend/game/game_settings.cpp and add the old default branch to LootSettings::oldDefaultBranches in src/backend/app/loot_settings.cpp.
    3. +
  3. Run lomad using lomad -t <github personal access token> -a -b <branch name> to (for all masterlists) create a branch for that release.
    4. +
  4. Update the default masterlist branch value and add the old value to GameSettings::oldDefaultBranches in src/backend/game/game_settings.cpp.

Release

@@ -27,5 +27,5 @@ title: Making A Release
  1. Post an announcement in the official forum thread.
    2. -
  2. Update the release notification message for all masterlists using lomad -t <github personal access token> -a -n <new version>.
    3. +
  3. Update the default branch and its release notification message for all masterlists using lomad -t <github personal access token> -a -d <branch name> -n <new version>.