Skip to content

Commit eec44d0

Browse files
dgp1130clydin
authored andcommitted
docs: remove Universal from caretaking doc
Since Universal code has been integrated into the Angular CLI repo, there are no longer any unique caretaking responsibilities. (cherry picked from commit 220a7e8)
1 parent e8c16c1 commit eec44d0

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed

docs/process/release.md

-10
Original file line numberDiff line numberDiff line change
@@ -24,10 +24,6 @@ The secondary caretaker does not have any _direct_ responsibilities, but they ma
2424
over the primary's responsibilities if the primary is unavailable for an extended time (a day
2525
or more) or in the event of an emergency.
2626

27-
The primary is also responsible for releasing
28-
[Angular Universal](https://github.com/angular/universal/), but _not_ responsible for merging
29-
PRs.
30-
3127
At the end of each caretaker's rotation, the primary should perform a handoff in which they
3228
provide information to the next caretaker about the current state of the repository and update
3329
the access group to now include the next caretakers. To perform this update to the access group,
@@ -111,9 +107,3 @@ Releases should be done in "reverse semver order", meaning they should follow:
111107
Oldest LTS -> Newest LTS -> Patch -> RC -> Next
112108

113109
This can skip any versions which don't need releases, so most weeks are just "Patch -> Next".
114-
115-
### Angular Universal
116-
117-
After CLI releases, the primary is also responsible for releasing Angular Universal if necessary.
118-
Follow [the instructions there](https://github.com/angular/universal/blob/main/docs/process/release.md)
119-
for the release process. If there are no changes to Universal, then the release can be skipped.

0 commit comments

Comments
 (0)