angular/dev-infra/release/versioning
Paul Gschwendtner 9dccaa9570 refactor(dev-infra): move common versioning tooling to shared location (#38656)
We initially added logic for determining active release trains into
the merge script. Given we now build more tools that rely on this
information, we move the logic into a more general "versioning" folder
that can contain common logic following the versioning document for the
Angular organization.

PR Close #38656
2020-09-28 16:11:40 -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 refactor(dev-infra): move common versioning tooling to shared location (#38656) 2020-09-28 16:11:40 -04:00
npm-registry.ts refactor(dev-infra): move common versioning tooling to shared location (#38656) 2020-09-28 16:11:40 -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

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.