-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
[docs/rfc] Define RFC merge process #11416
base: main
Are you sure you want to change the base?
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #11416 +/- ##
========================================
Coverage 92.14% 92.14%
========================================
Files 432 433 +1
Lines 20255 20389 +134
========================================
+ Hits 18663 18787 +124
- Misses 1230 1238 +8
- Partials 362 364 +2 ☔ View full report in Codecov by Sentry. |
cc @open-telemetry/collector-approvers |
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.
Non-blocking suggestions
- Add labels `rfc:final-comment-period` and `rfc:vote-needed` and indicate its usage. - Modify last section to apply same rules for modifying existing RFCs - Make re-requesting reviews mandatory
Co-authored-by: Alex Boten <223565+codeboten@users.noreply.github.com>
Co-authored-by: Evan Bradley <11745660+evan-bradley@users.noreply.github.com>
Description
Define RFC merge process in the
docs/rfc/README.md
. This is meant to be a tool for making decisions about hard stuff :)