From 69d374635fd57092c26ee488375a3164c9ded81d Mon Sep 17 00:00:00 2001 From: Alex Rickabaugh Date: Wed, 18 May 2022 16:16:37 -0700 Subject: [PATCH] docs: replace Angular Labs with Developer Preview docs (#46050) This commit updates the releasing/versioning doc on angular.io to cover the new "Developer Preview" concept. This replaces the old section on the no- longer-relevant "Angular Labs". PR Close #46050 --- aio/content/guide/releases.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/aio/content/guide/releases.md b/aio/content/guide/releases.md index 3f9e25d688e..d9319e54fa8 100644 --- a/aio/content/guide/releases.md +++ b/aio/content/guide/releases.md @@ -161,15 +161,15 @@ For details, see [Supported Public API Surface of Angular](https://github.com/an Any changes to the public API surface are done using the versioning, support, and depreciation policies previously described. - + -## Angular Labs +## Developer Preview -Angular Labs is an initiative to cultivate new features and iterate on them quickly. -Angular Labs provides a safe place for exploration and experimentation by the Angular team. +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. -Angular Labs projects are not ready for production use, and no commitment is made to bring them to production. -The policies and practices that are described in this document do not apply to Angular Labs projects. +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.