shift to maintenance mode (#3255)

Signed-off-by: Jordan Keister <[email protected]>

.github/ISSUE_TEMPLATE.md

@@ -2,4 +2,9 @@
 Thanks for filing an issue! Before you submit, please read the following:
 
 Check the other issue templates if you are trying to submit a bug report, feature request, or question. Search open/closed issues before submitting since someone might have asked the same thing before!
+
+!!
+Please note that since this repository is in maintenance mode, we will not accept any feature requests or non-critical issue reports.  
+!!
+
 -->

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,8 @@
 blank_issues_enabled: false
 contact_links:
+  - name: Feature Requests
+    url: https://github.com/operator-framework/operator-controller/issues/new/choose
+    about: Please open any feature requests against OLMv1 version instead
   - name: OLM Kubernetes Slack Channel
     url: https://kubernetes.slack.com/archives/C0181L6JYQ2
     about: Join the "#olm-dev" channel on the kubernetes slack - it's a good place to ask OLM-related questions!

README.md

@@ -6,6 +6,20 @@
 [![Go Report Card](https://goreportcard.com/badge/github.com/operator-framework/operator-lifecycle-manager)](https://goreportcard.com/report/github.com/operator-framework/operator-lifecycle-manager)
 [![Slack Channel](https://img.shields.io/badge/chat-4A154B?logo=slack&logoColor=white "Slack Channel")](https://kubernetes.slack.com/archives/C0181L6JYQ2)
 
+---
+> [!WARNING]  
+> This repository is associated with **Operator Lifecycle Manager** version 0 (v0) which is in maintenance mode. The community is excited to be working on a new design (v1) which intends to overcome a number of limitations of the v0 architecture, the primary repository for which is [operator controller](https://www.github.com/operator-framework/operator-controller).  
+
+In maintenance mode, we have the following changes to support expectations:
+1. We will accept no new features.
+2. We will accept no non-critical outage issues, defined here as a cluster-wide outage with no workaround.
+3. We will close backlog issues which do not meet the above criteria.
+4. We will continue to update the project to address emergent vulnerabilities on a best-effort basis.
+
+If you have any questions, please engage with us: [![Slack Channel](https://img.shields.io/badge/chat-4A154B?logo=slack&logoColor=white "Slack Channel")](https://kubernetes.slack.com/archives/C0181L6JYQ2)
+
+---
+
 ## Documentation
 
 User documentation can be found on the [OLM website][olm-docs].