Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AWS CDK public roadmap #450

Closed
2 of 11 tasks
evgenyka opened this issue Aug 8, 2022 · 0 comments
Closed
2 of 11 tasks

AWS CDK public roadmap #450

evgenyka opened this issue Aug 8, 2022 · 0 comments
Labels
bar-raiser/needed management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.

Comments

@evgenyka
Copy link

evgenyka commented Aug 8, 2022

Description

Suggested approach and method to publish public roadmap for the CDK.
Rendered RFC

Roles

Role User
Proposed by @evgenyka
Author(s) @evgenyka
API Bar Raiser TBD
Stakeholders @cgarvis, @RomainMuller, @iliapolo , @rix0rrr

See RFC Process for details

Workflow

  • Tracking issue created (label: status/proposed)
  • API bar raiser assigned (ping us at #aws-cdk-rfcs if needed)
  • Kick off meeting
  • RFC pull request submitted (label: status/review)
  • Community reach out (via Slack and/or Twitter)
  • API signed-off (label api-approved applied to pull request)
  • Final comments period (label: status/final-comments-period)
  • Approved and merged (label: status/approved)
  • Execution plan submitted (label: status/planning)
  • Plan approved and merged (label: status/implementing)
  • Implementation complete (label: status/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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bar-raiser/needed management/tracking status/stale The RFC did not get any significant enough progress or tracking and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants