-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
[chore][docs/rfc] Add text regarding conversations #11738
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 #11738 +/- ##
=======================================
Coverage 91.61% 91.61%
=======================================
Files 443 443
Lines 23770 23770
=======================================
Hits 21776 21776
Misses 1620 1620
Partials 374 374 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
**4 business days** after making the announcement to merge the RFC. | ||
comment. They will need to add a `rfc:final-comment-period` label to the PR, comment on the PR | ||
and note the final comment period in the #otel-collector-dev CNCF Slack channel, and wait for at | ||
least **4 business days** after making the announcement to merge the RFC. |
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.
I worry the idea of business days might be fuzzy considering the amount of approvers/maintainers in different geos.
Would it make more sense to say 5 days (this would account for plus or minus a day depending on which part of the world you're in)?
Description
Based on the experience of this process going through once, I am suggesting we make the following changes:
Link to tracking issue
Fixes #11737