From 532ccb647cab53bc2f70758a678b2a8157a98da1 Mon Sep 17 00:00:00 2001 From: Stephen Fluin Date: Thu, 30 Jan 2020 10:25:30 -0800 Subject: [PATCH] docs: remove the release schedule from docs (#34474) Removing for now, since the info is stale, and we need to determine how to adjust the schedule due to the unexpected and significant version 9 delay. PR Close #34474 --- aio/content/guide/releases.md | 29 +++++++---------------------- aio/content/guide/updating.md | 2 -- 2 files changed, 7 insertions(+), 24 deletions(-) diff --git a/aio/content/guide/releases.md b/aio/content/guide/releases.md index 4b51e7ff5f..5b40251620 100644 --- a/aio/content/guide/releases.md +++ b/aio/content/guide/releases.md @@ -72,6 +72,12 @@ The next version of the documentation is available at [next.angular.io](https:// We work toward a regular schedule of releases, so that you can plan and coordinate your updates with the continuing evolution of Angular. +
+ +Disclaimer: Dates are offered as general guidance and will be adjusted by us when necessary to ensure delivery of a high-quality platform. + +
+ In general, you can expect the following release cycle: * A major release every 6 months @@ -84,27 +90,6 @@ This cadence of releases gives you access to new features as soon as they are re -{@a schedule} -## Release schedule - -
- -Disclaimer: The dates are offered as general guidance and may be adjusted by us when necessary to ensure delivery of a high-quality platform. - -
- -The following table contains our current target release dates for the next two major versions of Angular: - - Date | Stable Release | Compatibility - ---------------------- | -------------- | ------------- - October/November 2019 | 9.0.0 | ^8.0.0 - May 2020 | 10.0.0 | ^9.0.0 - - Compatibility note: The primary goal of the backward compatibility promise is to ensure that changes in the core framework and tooling don't break the existing ecosystem of components and applications and don't put undue upgrade/migration burden on Angular application and component authors. - - - - {@a lts} {@a support} ## Support policy and schedule @@ -142,7 +127,7 @@ To help ensure that you have sufficient time and a clear path to update, this is * **Announcement:** We announce deprecated APIs and features in the [change log](https://github.com/angular/angular/blob/master/CHANGELOG.md "Angular change log"). Deprecated APIs appear in the [documentation](api?status=deprecated) with ~~strikethrough.~~ When we announce a deprecation, we also announce a recommended update path. For convenience, [Deprecations](guide/deprecations) contains a summary of deprecated APIs and features. -* **Deprecation period:** When an API or a feature is deprecated, it will still be present in the [next two major releases](#schedule). After that, deprecated APIs and features will be candidates for removal. A deprecation can be announced in any release, but the removal of a deprecated API or feature will happen only in major release. Until a deprecated API or feature is removed, it will be maintained according to the LTS support policy, meaning that only critical and security issues will be fixed. +* **Deprecation period:** When an API or a feature is deprecated, it will still be present in the next two major releases. After that, deprecated APIs and features will be candidates for removal. A deprecation can be announced in any release, but the removal of a deprecated API or feature will happen only in major release. Until a deprecated API or feature is removed, it will be maintained according to the LTS support policy, meaning that only critical and security issues will be fixed. * **npm dependencies:** We only make npm dependency updates that require changes to your apps in a major release. diff --git a/aio/content/guide/updating.md b/aio/content/guide/updating.md index ad62098e38..12ae88d486 100644 --- a/aio/content/guide/updating.md +++ b/aio/content/guide/updating.md @@ -68,5 +68,3 @@ For simple updates, the CLI command [`ng update`](cli/update) is all you need. W * Update command reference: [Angular CLI `ng update` command reference](cli/update) * Versioning, release, support, and deprecation practices: [Angular versioning and releases](guide/releases "Angular versioning and releases") - -* Release schedule: [Angular versioning and releases](guide/releases#schedule "Angular versioning and releases")