community/sig-release
Linus Arver cd82abf431 Add explicit links to release-engineering in sig-release
It's confusing having two links for the release-engineering subproject
without any description of each. The k/release repo houses all of the
existing tooling, such as anago, while the k/sig-release repo houses the
procedures and processes. Add these links explicitly to the description
so that newcomers have a clearer idea of where to get started.
2019-02-12 16:07:34 -08:00
..
OWNERS Updated OWNERS files to include link to docs 2019-01-30 19:37:21 +01:00
README.md Add explicit links to release-engineering in sig-release 2019-02-12 16:07:34 -08:00
charter.md Add SIG Release charter 2018-11-08 17:09:23 -05:00

README.md

Release Special Interest Group

The charter defines the scope and governance of the Release Special Interest Group.

Meetings

Leadership

Chairs

The Chairs of the SIG run operations and processes governing the SIG.

Emeritus Leads

  • Jaice Singer DuMars (@jdumars), Google

Contact

Subprojects

The following subprojects are owned by sig-release:

GitHub Teams

The below teams can be mentioned on issues and PRs in order to get attention from the right people. Note that the links to display team membership will only work if you are a member of the org.

Team Name Details Description
@kubernetes/sig-release link SIG Release Members
@kubernetes/sig-release-admins link Admins for SIG Release repositories
@kubernetes/kubernetes-milestone-maintainers link Milestone Maintainers
@kubernetes/kubernetes-release-managers link Release Managers

The canonical location for SIG Release information is k/sig-release.