From 59c5708db18984a5dba6f6f48bd4595a371d0c0e Mon Sep 17 00:00:00 2001 From: Carlos Alberto Cortez Date: Fri, 22 Nov 2024 14:29:45 +0100 Subject: [PATCH] Add a note about OTEPs moving to the Specification. (#268) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Trask Stalnaker Co-authored-by: Robert PajÄ…k --- README.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/README.md b/README.md index 0e8de45e1..28f71820c 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,11 @@ [![Slack chat][slack-image]][slack-url] [![Build Status][circleci-image]][circleci-url] +> [!WARNING] +> OTEPs have been moved to the [Specification](https://github.com/open-telemetry/opentelemetry-specification/tree/main/oteps/) +> repository. This repository has been preserved for reference purposes. +> Please otherwise refer to the Specification. + ## Evolving OpenTelemetry at the speed of Markdown OpenTelemetry uses an "OTEP" (similar to a RFC) process for proposing changes to the [OpenTelemetry specification](https://github.com/open-telemetry/opentelemetry-specification).