docs: add mention of GH issue for devPreview feedback (angular#60010)

fixes angular#59902

PR Close angular#60010

Author: JeanMeche

adev/src/content/reference/releases.md

@@ -159,10 +159,12 @@ For example, to update from version 10 to version 12:
 
 Occasionally we introduce new APIs under the label of "Developer Preview". These are APIs that are fully functional and polished, but that we are not ready to stabilize under our normal deprecation policy.
 
-This may be because we want to gather feedback from real applications before stabilization, or because the associated documentation or migration tooling is not fully complete.
+This may be because we want to gather feedback from real applications before stabilization, or because the associated documentation or migration tooling is not fully complete. Feedback can be provided via a [GitHub issue](https://github.com/angular/angular/issues), where developers can share their experiences, report bugs, or suggest improvements to help refine the feature.
 
 The policies and practices that are described in this document do not apply to APIs marked as Developer Preview. Such APIs can change at any time, even in new patch versions of the framework. Teams should decide for themselves whether the benefits of using Developer Preview APIs are worth the risk of breaking changes outside of our normal use of semantic versioning.
 
+
+
 ## Experimental
 
 These APIs might not become stable at all or have significant changes before becoming stable.