honeymoose/angular-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
angular-cn/dev-infra/release/versioning
History
Paul Gschwendtner 474ecf6d00 feat(dev-infra): add logic for printing active release trains (#38656) 
Adds a method for printing active release trains for a configured
project. This is helpful for the release tool that will print
the active release trains. Also this can be useful for the
caretaker status command, where we could print the active
version branches (i.e. "is there currently a feature-freeze branch").

PR Close #38656
2020-09-28 16:11:41 -04:00
..
active-release-trains.ts
refactor(dev-infra): move common versioning tooling to shared location (#38656)
2020-09-28 16:11:40 -04:00
BUILD.bazel
refactor(dev-infra): move common versioning tooling to shared location (#38656)
2020-09-28 16:11:40 -04:00
index.ts
refactor(dev-infra): move common versioning tooling to shared location (#38656)
2020-09-28 16:11:40 -04:00
long-term-support.ts
feat(dev-infra): add logic for determining active LTS branches (#38656)
2020-09-28 16:11:41 -04:00
npm-registry.ts
refactor(dev-infra): move common versioning tooling to shared location (#38656)
2020-09-28 16:11:40 -04:00
print-active-trains.ts
feat(dev-infra): add logic for printing active release trains (#38656)
2020-09-28 16:11:41 -04:00
README.md
refactor(dev-infra): move common versioning tooling to shared location (#38656)
2020-09-28 16:11:40 -04:00
release-trains.ts
refactor(dev-infra): move common versioning tooling to shared location (#38656)
2020-09-28 16:11:40 -04:00
version-branches.ts
refactor(dev-infra): move common versioning tooling to shared location (#38656)
2020-09-28 16:11:40 -04:00

README.md

Versioning for the Angular organization

The folder contains common tooling needed for implementing the versioning as proposed by this design document. Primary tooling is the determination of active release trains.