This document provides a step-by-step list to remind Orca
maintainers how to make a release.

The general instructions for a release are here:

  https://handbook.gnome.org/maintainers/making-a-release.html

Here's a summary for Orca:

PREPARE SOURCES FOR THE RELEASE:
-------------------------------

Make sure you are up to date:

  git pull
  git status

Update ./NEWS with changes from the last tagged release. You can use
commands like the following:

Detailed commits since the 48.beta tag:

  git log 48.beta..

Short list of translation changes with author names and files:

  git log 48.beta.. --grep translation --pretty=format:"%s - %an" --name-only

Quick-and-dirty formatted list of translation changes:

  git log 48.beta.. --grep translation --pretty=format:"%s,%an" --name-only |
    awk -F/ '/\.po/ {gsub("\\.po", "", $NF); printf(",%s",$NF); next;}
    {gsub("(Updated* |Add(ed)* | translation| help)", "", $0); printf("\n%s",$0);}' |
    awk -F, '!seen[$0]++ {if (NF == 3) printf("  %-15s %-25s %s\n", $3, $1, $2);}' |
    sort

Short list of non-translation commits:

  git log 48.beta.. --grep translation --invert-grep --pretty=format:" * %s%n"

NOTE: You should also make sure the external dependencies listed in
meson.build and README.md are accurate.

COMMIT RELEASE CHANGES AND TAG THE RELEASE, TRIGGERING A RELEASE BUILD:
-----------------------------------------------------------------------

git commit -a
git push
git tag -a -s 48.rc
git push origin 48.rc

BUMP THE VERSION:
-----------------

Modify this line in ./meson.build:

    version: '48.rc'

The major version (48) increments by 1 each new GNOME release cycle.
The minor version proceeds as follows: alpha, beta, rc, 0, 1, 2, 3, etc.

Modify ./README.md to make sure it has the right Orca version.

If this is a .0 release, modify this line in .gitlab/issue_templates/Default.md:

   *Note that versions prior to version XX.x are unsupported for non-critical issues.*

setting "XX" to the major release preceding this one.

git commit -a
git push
