-
Notifications
You must be signed in to change notification settings - Fork 208
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
Update updating OpenTelemetry Collector dependencies doc #2049
base: main
Are you sure you want to change the base?
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 <131809008+clayton-cornell@users.noreply.github.com>
Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com>
Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com>
Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com>
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 |
No description provided.