Reflect status of each component #1694
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lalitb
reviewed
Apr 30, 2024
lalitb
approved these changes
Apr 30, 2024
|
Merging quickly as this is not changing any status, but just adding breakdown. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed in previous community meetings, the main readme is now updated to show the status of individual components as opposed to the overall signal. This gives better transparency, and additionally, we expect API to always stabilize before SDK, so it is easy to reflect them with a breakdown.
Only showing the API/SDK/OTLP Exporter (Plus one appender for logs, without which logs are not really useable) for each signal as we are prioritizing them for initial GA release. (The list could change, and can be updated accordingly)