Lift the Feature Freeze (#12001)

Author: Maffooch

.github/ISSUE_TEMPLATE/feature_request.md

@@ -8,7 +8,7 @@ assignees: ''
 ---
 ## :warning: Note on feature completeness :warning:
 
-We are narrowing the scope of acceptable enhancements to DefectDojo in preparation for v3. Learn more here:
+We are narrowing the scope of acceptable enhancements to DefectDojo. Learn more here:
 https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md
 
 **Is your feature request related to a problem? Please describe**

README.md

@@ -107,9 +107,8 @@ our channel there, [#defectdojo](https://owasp.slack.com/channels/defectdojo). F
 
 ## Contributing
 
-:warning: We have instituted a [feature freeze](https://github.com/DefectDojo/django-DefectDojo/discussions/8002) on v2
-of DefectDojo as we begin work on v3. Please see our [contributing guidelines](readme-docs/CONTRIBUTING.md) for more
-information. Check out our latest update on v3 [here](https://github.com/DefectDojo/django-DefectDojo/discussions/11199).
+Please see our [contributing guidelines](readme-docs/CONTRIBUTING.md) for more
+information.
 
 ## Pro Edition
 [Upgrade to DefectDojo Pro](https://www.defectdojo.com/) today to take your DevSecOps to 11. DefectDojo Pro is

readme-docs/CONTRIBUTING.md

@@ -18,16 +18,9 @@ Bugs that do not have this information will be closed.
 
 Here are a few things to keep in mind when making changes to DefectDojo.
 
-## Submission Pre-Approval -- DefectDojo is Feature Complete
-
-We are narrowing the scope of new additions to DefectDojo v2 in order to stabilize the API and data model for v3.
-Generally speaking, we will no longer accept new API routes, UI routes or views, or new models. One exception is that we
-**will** still accept new parsers and improvements to existing fields/functionality. Simple updates to the data model
-are acceptable as long as they do not introduce additional complexity, until the community has agreed on a "data model
-freeze date", at which point we will stop accepting updates adding new fields or changing existing fields for any reason
-other than bugfixes or stability improvements/etc. Once v3 is released, no further data model updates to v2 will be
-approved. We don't want to waste your time, so if you're unsure whether your hypothetical enhancement meets the criteria
-for approval, please file an issue to get pre-approval before beginning work on a PR. If approved, we will add the
+## Submission Pre-Approval
+
+We don't want to waste your time, so if you're unsure whether your hypothetical enhancement meets the criteria for approval, please file an issue to get pre-approval before beginning work on a PR. If approved, we will add the
 `enhancement-approved` label to your issue and you can begin building it out.
 
 Below are some representative examples of what we will and won't support going forward. If you have suggestions or other