From f1a6e783cd1c0f9f829564d2c8921778a7e0e61c Mon Sep 17 00:00:00 2001
From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com>
Date: Tue, 21 Jan 2025 15:48:27 +0000
Subject: [PATCH 1/2] doc: Release: Add backport policy

Add Policy discussed and agreed between maintainers
---
 RELEASE.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/RELEASE.md b/RELEASE.md
index 9b221cbed..c65f44e3f 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -54,3 +54,21 @@ git push upstream v1.2.0
 
 ### Post-Steps
 Once the tag has been pushed the release action should run automatically. You can view the progress [here](https://github.com/operator-framework/operator-controller/actions/workflows/release.yaml). When finished, the release should then be available on the [releases page](https://github.com/operator-framework/operator-controller/releases).
+
+
+## Backporting Policy
+
+Mainly critical issue fixes might be backported to the most recent minor release.
+Special backport requests can be discussed during the weekly Community meeting or via Slack channel;
+this does not guarantee an exceptional backport will be created.
+
+Occasionally non-critical issue fixes will be backported, either at an approver’s discretion or by request as noted above.
+If you believe an issue should be backported, please feel free to reach out and raise your concerns or needs.
+For information on contacting maintainers via the [#olm-dev](https://kubernetes.slack.com/archives/C0181L6JYQ2) Slack channel
+and attending meetings. To know more about see [How to Contribute](./CONTRIBUTING.md).
+
+### Process
+
+1. Create a PR with the fix cherry-picked into the release branch
+2. Ask for a review from the maintainers.
+3. Once approved, merge the PR and perform the Patch Release steps above.
\ No newline at end of file

From fa69bdea117cddefff00331973582ece216b61e7 Mon Sep 17 00:00:00 2001
From: Camila Macedo <7708031+camilamacedo86@users.noreply.github.com>
Date: Wed, 29 Jan 2025 17:44:37 +0000
Subject: [PATCH 2/2] Apply suggestions from code review

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

diff --git a/RELEASE.md b/RELEASE.md
index c65f44e3f..06510b63f 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -58,7 +58,7 @@ Once the tag has been pushed the release action should run automatically. You ca
 
 ## Backporting Policy
 
-Mainly critical issue fixes might be backported to the most recent minor release.
+Significant security and critical bug fixes can be backported to the most recent minor release.
 Special backport requests can be discussed during the weekly Community meeting or via Slack channel;
 this does not guarantee an exceptional backport will be created.