Update updating OpenTelemetry Collector dependencies doc #2049
Conversation
|
Should we define a specific window of time that we're going to allow for community maintainers before we can opt to disable/remove the component from that release if it's too much effort? |
Co-authored-by: Clayton Cornell <[email protected]>
Co-authored-by: Clayton Cornell <[email protected]>
Co-authored-by: Clayton Cornell <[email protected]>
Co-authored-by: Clayton Cornell <[email protected]>
disabeling/removing the component is really a last resort option that I hope we don't ever have to take. If community maintainers are not available to solve some breaking changes, we should be able to quickly solve them (doing the minimum to get it to build and run should be easy in most cases, in the end these are just wrappers around the otel components). I'd prefer to not specify a time window for now and do case-by-case |
|
|
||
| You can find the community contributor GitHub handles at the top of the community component files (the components that have "Community" set to true). | ||
| Once the PR is created, you can ping them in the PR and message them on Slack. Each contributor should create a PR in your branch with the updated component. | ||
| Notify the contributors a few days before the release so they have enough time to do the update. |
There was a problem hiding this comment.
Most of the time when you read these docs you will be doing the release, so I'm not sure if it's the right place for a reminder like this.
There was a problem hiding this comment.
this is the "updating-otel" doc. The update should be done prior to the release and should be started at least one week before cutting the RC
No description provided.