From f0f85dbe2f4c437ebe080ead60ebd6bfb7ea491e Mon Sep 17 00:00:00 2001 From: Jens Kuehlers Date: Fri, 17 May 2024 16:16:22 +0000 Subject: [PATCH] docs: Include info about experimental on adev (#55857) Copy information about meaning of "experimental" from angular.io to angular.dev. PR Close #55857 --- adev/src/content/reference/releases.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/adev/src/content/reference/releases.md b/adev/src/content/reference/releases.md index f925e238abc..0be4423505f 100644 --- a/adev/src/content/reference/releases.md +++ b/adev/src/content/reference/releases.md @@ -163,3 +163,9 @@ Occasionally we introduce new APIs under the label of "Developer Preview". These 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. 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 are APIs might not become stable at all or have significant changes before becoming stable. + +The policies and practices that are described in this document do not apply to APIs marked as experimental. 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 experimental APIs are worth the risk of breaking changes outside of our normal use of semantic versioning.