Update release_template with step to update next release's manifest.

[mch2]

Signed-off-by: Marc Handalian handalm@amazon.com

Description

Updates the release template with a step to update the next release's manifest.

Issues Resolved

related - opensearch-project/OpenSearch#1317
closes #1140

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[gaiksaya]

Should the nightly's be pointing to main as component's ref when a new manifest is created? And then change to 1.3 branch at T-14 days?

[codecov-commenter]

Codecov Report

Merging #1139 (3bcbd6d) into main (c0490fb) will increase coverage by 0.52%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main    #1139      +/-   ##
============================================
+ Coverage     93.49%   94.01%   +0.52%     
============================================
  Files           100       92       -8     
  Lines          2551     2489      -62     
  Branches          7        0       -7     
============================================
- Hits           2385     2340      -45     
+ Misses          158      149       -9     
+ Partials          8        0       -8     

Impacted Files	Coverage Δ
tests/jenkins/jobs/BuildManifest_Jenkinsfile
tests/jenkins/jobs/InputManifest_Jenkinsfile
tests/jenkins/jobs/Hello_Jenkinsfile
src/jenkins/BuildManifest.groovy
tests/jenkins/jobs/Messages_Jenkinsfile
tests/jenkins/jobs/Vars_Jenkinsfile
src/jenkins/InputManifest.groovy
src/jenkins/Messages.groovy

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c0490fb...3bcbd6d. Read the comment docs.

[mch2]

Should the nightly's be pointing to main of component's ref when a new manifest is created? And then change to 1.3 branch at T-14 days?

That makes sense for major releases but not for minor. If the plugin repo is following the correct branching strategy we could do this for minors as well and set them to (version.x) branch.
@gaiksaya I should have cut this initially as an issue - lets chat on #1140.

[dblock]

I don't think we need this. It's a step in the next release's checklist.