You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# Use this changelog template to create an entry for release notes.
2
+
3
+
# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
4
+
change_type: new_component
5
+
6
+
# The name of the component, or a single word describing the area of concern, (e.g. otlpreceiver)
7
+
component: datadog/extension
8
+
9
+
# A brief description of the change. Surround your text with quotes ("") if it needs to start with a backtick (`).
10
+
note: "Release datadog extension. See README for details: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/datadogextension/README.md"
11
+
12
+
# One or more tracking issues or pull requests related to the change
13
+
issues: [983]
14
+
15
+
# (Optional) One or more lines of additional information to render under the primary note.
16
+
# These lines will be padded with 2 spaces and then inserted directly into the document.
17
+
# Use pipe (|) for multiline entries.
18
+
subtext:
19
+
20
+
# Optional: The change log or logs in which this entry should be included.
21
+
# e.g. '[user]' or '[user, api]'
22
+
# Include 'user' if the change is relevant to end users.
23
+
# Include 'api' if there is a change to a library API.
Copy file name to clipboardExpand all lines: distributions/README.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,10 +12,13 @@ Distributions supported by the Collector SIG should fulfill the following criter
12
12
4. May be focused on development or proof of concept use cases. The distribution should clearly indicate whether the Collector SIG recommends the distribution be used in production environments.
13
13
5. Must only include components from the `open-telemetry` org.
14
14
- Components that are marked [Unmaintained](https://github.com/open-telemetry/opentelemetry-collector#unmaintained) will be kept in any distributions for six months. After six months of being unmaintained the component will be removed from the distributions.
15
-
6. Have a clearly defined list of criteria for which components are included.
16
-
7. Must include the following assets except where the specific purpose of the distribution is naturally associated with a subset of these assets. In such cases, it should be clearly stated which assets are skipped and why. Additional assets may be included if the maintainers agree:
15
+
6. Must only include components that are properly tagged as Go modules. Updates to components will only be considered if they correspond to a tag.
16
+
7. Have a clearly defined list of criteria for which components are included.
17
+
8. Must include the following assets except where the specific purpose of the distribution is naturally associated with a subset of these assets. In such cases, it should be clearly stated which assets are skipped and why. Additional assets may be included if the maintainers agree:
17
18
- Binaries for linux_amd64, linux_arm64, windows_amd64 and darwin_arm64
18
19
- linux_amd64 and linux_arm64 container images
19
20
- Packages to be used with Linux distributions (RPM, deb), macOS (brew), Windows (MSI) for each distributed binary.
20
21
21
-
22
+
After any change to these rules, distribution owners will have 1 month to comply with any new requirements.
23
+
Maintainers will make a best effort to ensure that distribution owners are notified of any changes to the rules that may affect their distribution.
24
+
If a distribution does not comply with the new requirements, it MAY be marked as deprecated after one month and eventually be removed from the list of supported distributions.
0 commit comments