![]() 12 months of long-term support (LTS), during which only critical fixes and security patches are released.6 months of active support, during which regularly-scheduled updates and patches are released.This cadence of releases gives you access to new features as soon as they are ready, while maintaining the stability and reliability of the platform for production users.Īll of our major releases are supported for 18 months. 1-3 minor releases for each major release.In general, you can expect the following release cycle: We work toward a regular schedule of releases, so that you can plan and coordinate your updates with the continuing evolution of Angular.ĭisclaimer: Dates are offered as general guidance and will be adjusted by us when necessary to ensure delivery of a high-quality platform. This includes any documentation for Beta or Release Candidate features and APIs. The next version of the documentation is available at. A release candidate is indicated by a release tag appended with the rc identifier, such as version 8.1.0-rc. Release candidate: A release that is feature complete and in final testing.A Beta release is indicated by a release tag appended with the beta identifier, such as 8.0.0-beta.0. Beta: A release that is under active development and testing. ![]() We let you preview what's coming by providing Beta releases and Release Candidates ( rc) for each major and minor release: See Keeping Up-to-Date for more information about updating your Angular projects to the most recent version. After successfully updating to 7.x.x, you can then update to 8.x.x. For example, if you want to update from version 6.x.x to version 8.x.x, we recommend that you update to the latest 7.x.x release first. Follow the instructions to incrementally update to the next major version, testing and validating at each step. If you are updating from one major version to another, then we recommend that you don't skip major versions.For example, you can update directly from 7.0.0 to 7.2.11. If you are updating within the same major version, then you can skip any intermediate versions and update directly to the targeted version.In alignment with the versioning scheme described above, we commit to support the following update paths: This means that in order to use the CLI as you develop an Angular app, the version of and the CLI need to be the same. Note: As of Angular version 7, the major versions of Angular core and the CLI are aligned. No developer assistance is expected during update. Patch releases are low risk, bug fix releases.We update peer dependencies in minor versions by expanding the supported versions, but we do not require projects to update these dependencies. Minor releases are fully backward-compatible no developer assistance is expected during update, but you can optionally modify your apps and libraries to begin using new APIs, features, and capabilities that were added in the release. Minor releases contain new smaller features.When updating to a new major release, you may need to run update scripts, refactor code, run additional tests, and learn new APIs. Major releases contain significant new features, some but minimal developer assistance is expected during the update.The version number is incremented based on the level of change included in the release. For example, version 7.2.11 indicates major version 7, minor version 2, and patch level 11. This use of semantic versioning helps you understand the potential impact of updating to a new version.Īngular version numbers have three parts:. AngularJS is the name for all v1.x versions of Angular.Īngular version numbers indicate the level of changes that are introduced by the release. If you are currently using AngularJS, see Upgrading from AngularJS. The practices described in this document apply to Angular 2.0 and later. We want everyone who depends on Angular to know when and how new features are added, and to be well-prepared when obsolete ones are removed. ![]() We strive to ensure that future changes are always introduced in a predictable way. This document contains the practices that we follow to provide you with a leading-edge app development platform, balanced with stability. We strive to ensure that the foundation on top of which you are building is continuously improving and enabling you to stay up-to-date with the rest of the web ecosystem and your user needs. We also share with you the desire for Angular to keep evolving. Stability is essential for the ecosystem around Angular to thrive. Stability ensures that reusable components and libraries, tutorials, tools, and learned practices don't become obsolete unexpectedly. We recognize that you need stability from the Angular framework. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |