Graham/angular-cli
1
0
Fork 0
mirror of https://github.com/angular/angular-cli.git synced 2025-05-16 18:43:42 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: Update policy on LTS fixes

Browse Source 
This commit adds guidance on when to merge commits into LTS branches and how PRs should be opened.
This commit is contained in:
Keen Yee Liau 2020-03-20 13:07:44 -07:00 committed by Douglas Parker
parent cad8154ba3
commit 75c5cb26af
1 changed files with 14 additions and 0 deletions

14
docs/process/release.md

@ -81,6 +81,20 @@ instance), then you will need to fetch the contributor's branch for your local
Git instance to have knowledge of the commit being cherry picked onto the patch
branch.
### Maintaining LTS branches
Releases that are under Long Term Support (LTS) are listed on [angular.io](https://angular.io/guide/releases#support-policy-and-schedule).
Since there could be more than one LTS branch at any one time, PR authors who want to
merge commits into LTS branches must open a pull request against the specific base branch they'd like to target.
In general, cherry picks for LTS should only be done if it meets one of the criteria below:
1. It addresses a critical security vulnerability.
2. It fixes a breaking change in the external environment.
For example, this could happen if one of the dependencies is deleted from NPM.
3. It fixes a legitimate failure on CI for a particular LTS branch.
# Release
## Before releasing