From 23120a923c2bd3ca182291df2080214fbd5f20ca Mon Sep 17 00:00:00 2001
From: Richard Gibson <richard.gibson@gmail.com>
Date: Tue, 26 Nov 2024 14:05:17 -0500
Subject: [PATCH] chore(.github): Add release verification prompts to PR
 template section "Upgrade Considerations" (#10444)

## Description
A topic in last week's kernel meeting was the burden of verifying releases, and even of determining _what_ to verify and _how_ to do so. This is an attempt to make that explicit at a much earlier point in development, with hints regarding future automation potential but no firm commitment of such. Assuming this lands, I expect release instructions to include collecting steps from all constituent PRs and post-release cleanup of any relevant scripts.

### Security Considerations
n/a

### Scaling Considerations
n/a

### Documentation Considerations
n/a

### Testing Considerations
n/a

### Upgrade Considerations
This is intended to increase the maturity of our upgrade process.
---
 .github/PULL_REQUEST_TEMPLATE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 40cda1dc8a9..dc1ce3900b3 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -32,4 +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? -->
+<!-- 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/. -->