skills/angular__angular
1
0
Fork 0
mirror of https://github.com/angular/angular.git synced 2026-09-14 13:54:52 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: replace Angular Labs with Developer Preview docs (#46050)

Browse Source 
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
This commit is contained in:
Alex Rickabaugh
2022-05-18 16:16:37 -07:00
parent 6d1e6a8bc7
commit 69d374635f
1 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
aio/content/guide/releases.md
+6 -6
View File
@@ -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.
<a id="labs"></a>
<a id="developer-preview"></a>
## 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.
<!-- links -->