MaintainersCorner/Releasing/MakeThingsEasier

• README: just don't put pieces of information in that file that need to be updated for each release.

  • For example the version number is anyway easy to find in the top-level meson.build file or equivalent.

• NEWS: you can update it from time to time, even outside releases, to summarize the next version.

• NEWS: “Translation updates” is sufficient, because it's hard to credit correctly the translator and the reviewer (all the information is usually not encoded in the git commit author and committer). The translators are already correctly credited in the individual *.po files, and the "translator-credits" is also used for that purpose.

Scripts and automation

• gitlab-changelog - Generates a NEWS/ChangeLog entry from git commits and GitLab issues/merge requests.

• upload-tarball.sh:

  #!/bin/sh
  scp "$1" USER@master.gnome.org:~
  ssh USER@master.gnome.org