Skip to content

Update KEP-1731 to include the latest implementation changes #2289

@xmudrii

Description

@xmudrii

We had to make some implementation changes for KEP-1731 (publishing packages to the community infra) along the way but these changes didn't made their way to the KEP. We need to ensure that the KEP is up to date as it might be used as the implementation reference in the future.

/assign
/sig release
/area release-eng
/priority important-soon

Metadata

Metadata

Assignees

Labels

area/release-engIssues or PRs related to the Release Engineering subprojectkind/documentationCategorizes issue or PR as related to documentation.lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/releaseCategorizes an issue or PR as relevant to SIG Release.

Type

No type

Projects

Status

🏗️ In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions