From 584306bf46372e0e800a1ece6ebe9827d19a864e Mon Sep 17 00:00:00 2001
From: Povilas Kanapickas <povilas@radix.lt>
Date: Fri, 5 Nov 2021 14:04:55 +0200
Subject: [PATCH 1/3] github: Add new releases to new issue template dialog

---
 .github/ISSUE_TEMPLATE/bug_report.yml | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 208e7058..d3639c68 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -30,6 +30,8 @@ body:
         - v2.3.2-alpha
         - v2.3.2
         - v2.3.3
+        - v2.3.4
+        - v2.4.0
         - From Git HEAD or commit (specify below)
     validations:
       required: true

From d874e5f729690055cf592f748f06e81cf59d7a73 Mon Sep 17 00:00:00 2001
From: Povilas Kanapickas <povilas@radix.lt>
Date: Fri, 5 Nov 2021 14:04:56 +0200
Subject: [PATCH 2/3] RELEASING: Add missing details about updating version
 numbers

---
 RELEASING.md | 23 ++++++++++++++++++++---
 1 file changed, 20 insertions(+), 3 deletions(-)

diff --git a/RELEASING.md b/RELEASING.md
index 741f54ae..021a4fa4 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -27,11 +27,28 @@ Check `newsfragments` directory for any forgotten release notes
 Step 3: Merge the release notes PR
 ----------------------------------
 
-Step 4: Push git tag
---------------------
+Step 4: Bump the version number
+-------------------------------
 
 Pull the merge commit created on the `master` branch during the step 2.
 
+Edit the following files and update the version numbers:
+
+ - `Build.properties`
+ - `cmake/Version.cmake`
+ - `doc/barrierc.1`
+ - `doc/barriers.1`
+ - `.github/ISSUE_TEMPLATE/bug_report.yml`
+
+Commit to the release branch with the following message `Barrier x.y.z`.
+
+Push the commit:
+
+    git push origin master
+
+Step 5: Push git tag
+--------------------
+
 Create a tag:
 
     git tag -s v${VERSION} -m v${VERSION}
@@ -41,7 +58,7 @@ Push the tag:
     git push origin master --tags
 
 
-Step 5: Draft a new release on Github
+Step 6: Draft a new release on Github
 -------------------------------------
 
 Go to https://github.com/buildbot/buildbot/releases and draft a new release.

From 40d4a58b1cedd9c06ecb5d30820a908979bb7f34 Mon Sep 17 00:00:00 2001
From: Povilas Kanapickas <povilas@radix.lt>
Date: Fri, 5 Nov 2021 14:04:57 +0200
Subject: [PATCH 3/3] RELEASING: Specify that newest macOS release dmg should
 be used

---
 RELEASING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RELEASING.md b/RELEASING.md
index 021a4fa4..6cfbafaa 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -70,7 +70,7 @@ Use the release notes generated by the `towncrier` tool as the description of th
 Upload the artifacts created by Azure pipelines as the binaries of the release. The following
 artifacts should be uploaded to Github:
 
- - the Barrier-X.Y.Z-release.dmg created by the oldest Mac OS task (artifact name is
+ - the Barrier-X.Y.Z-release.dmg created by the newest Mac OS task (artifact name is
    "Mac Release Disk Image and App XYZ").
 
  - the BarrierSetup-X.Y.Z-release.exe (artifact name is Windows Release Installer).