From 11ddfbd5f2f44018b79b49e48d81d5dfb2b99c11 Mon Sep 17 00:00:00 2001
From: Richard Gibson <richard.gibson@gmail.com>
Date: Mon, 11 Nov 2024 10:10:30 -0500
Subject: [PATCH 1/2] chore(.github): Add "Release Verification" to the PR
 template

---
 .github/PULL_REQUEST_TEMPLATE.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 40cda1dc8a9..c3fb24934cb 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -33,3 +33,6 @@ refs: #XXXX
 
 ### Upgrade Considerations
 <!-- What aspects of this PR are relevant to upgrading live production systems, and how should they be addressed? -->
+
+### Release Verification
+<!-- What steps should be followed to verify that these changes have been included in a release (ollinet/emerynet/mainnet/etc.) and work successfully there? If the process is elaborate, consider adding a script to scripts/verification/. -->

From efce9a32f880ae75f8f97569169e5176b5299b0a Mon Sep 17 00:00:00 2001
From: Richard Gibson <richard.gibson@gmail.com>
Date: Mon, 11 Nov 2024 15:09:55 -0500
Subject: [PATCH 2/2] chore(.github): Incorporate the new prompts into Upgrade
 Considerations

---
 .github/PULL_REQUEST_TEMPLATE.md | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index c3fb24934cb..dc1ce3900b3 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -32,7 +32,4 @@ refs: #XXXX
 <!-- Every PR should of course come with tests of its own functionality. What additional tests are still needed beyond those unit tests? How does this affect CI, other test automation, or the testnet? -->
 
 ### Upgrade Considerations
-<!-- What aspects of this PR are relevant to upgrading live production systems, and how should they be addressed? -->
-
-### Release Verification
-<!-- What steps should be followed to verify that these changes have been included in a release (ollinet/emerynet/mainnet/etc.) and work successfully there? If the process is elaborate, consider adding a script to scripts/verification/. -->
+<!-- What aspects of this PR are relevant to upgrading live production systems, and how should they be addressed? What steps should be followed to verify that its changes have been included in a release (ollinet/emerynet/mainnet/etc.) and work successfully there? If the process is elaborate, consider adding a script to scripts/verification/. -->