name | about | title | labels | assignees |
---|---|---|---|---|
RFC |
Propose a significant change to the cdk8s toolchain |
RFC | describe your RFC |
rfc/proposed |
Short description of the proposed feature.
Role | User |
---|---|
Proposed by | @alias |
Author(s) | @alias, @alias, @alias |
API Bar Raiser | @alias |
Stakeholders | @alias, @alias, @alias |
See RFC Process for details
- Tracking issue created (label:
rfc/proposed
) - API bar raiser assigned (ping us at #cdk8s if needed)
- Kick off meeting
- RFC pull request submitted (label:
rfc/review
) - Community reach out (via Slack and/or Twitter)
- API signed-off (label
rfc/api-approved
applied to pull request) - Final comments period (label:
rfc/final-comments-period
) - Approved and merged (label:
rfc/approved
) - Execution plan submitted (label:
rfc/planning
) - Plan approved and merged (label:
rfc/implementing
) - Implementation complete (label:
rfc/done
)
Author is responsible to progress the RFC according to this checklist, and apply the relevant labels to this issue so that the RFC table in README gets updated.