-
Notifications
You must be signed in to change notification settings - Fork 83
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
RFC 53: updates to RFC process #336
Conversation
As a follow up to a retrospective the CDK team has performed about the RFC process. This PR proposes the following changes: [ADD]
Co-authored-by: Niranjan Jayakar <nija@amazon.com>
Co-authored-by: Niranjan Jayakar <nija@amazon.com>
From our conversation amongst CDK tech leads: we will reframe the RFC process to use an “API Bar Raiser” model instead of an approver model. Every RFC will get assigned a “tier” and bar raiser for API Bar Raising by the CDK Tech Leadership (email aws-cdk-tech-leads@).
The alias of the bar raiser will be included in the RFC document itself and the same bar raiser will be required if major API changes are performed. As for the rest of the RFC, the RFC PR will undergo the normal PR process of the CDK team, which means that an approver from the core team will eventually need to approve the PR in order to merge it. The API bar raiser will need to sign-off on the “working backwards” section, which primarily represents the public API of the feature. |
Co-authored-by: Romain Marcadier <rmuller@amazon.com>
Co-authored-by: Romain Marcadier <rmuller@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! I think the new "StackSets support" RFC might be a good candidate to try out this new process on.
I guess the only irritating part is that the template is changing, so the author might have to do some work to move to the new template...
Yes, let's apply this scheme to this RFC! |
As a follow up to a retrospective the CDK team has performed about the RFC process.
This PR proposes the following changes:
See https://github.com/cdklabs/team-internal/pull/18 for internal process changes.