Add moratorium on relying on schema transformations for telemetry sta…

…bility

CHANGELOG.md

@@ -25,6 +25,9 @@ release.
 
 ### Semantic Conventions
 
+- Add moratorium on relying on schema transformations for telemetry stability
+  ([#3380](https://github.com/open-telemetry/opentelemetry-specification/pull/3380))
+
 ### Compatibility
 
 ### OpenTelemetry Protocol

specification/telemetry-stability.md

@@ -49,6 +49,9 @@ coming from an unstable instrumentation.
 
 ## Stable Instrumentations
 
+> **Warning**
+> There is a moratorium on relying on schema transformations for telemetry stability.
+
 Stable telemetry-producing instrumentations (stable instrumentations for short) SHOULD
 be clearly labeled so by any means the instrumentations authors consider idiomatic for
 their language, e.g. via version numbers, artifact names, documentation, etc.
@@ -80,18 +83,15 @@ Stable instrumentations that include the Schema URL in the produced telemetry ar
 called Schema-File Driven Telemetry Producers.
 
 Such instrumentations are prohibited from changing the produced telemetry until
-April 1, 2023 and until that date are subject to exactly the same restrictions as
+the moratorium on relying on schema transformations for telemetry stability is lifted
+and until that date are subject to exactly the same restrictions as
 [Fixed Schema Telemetry Producers](#fixed-schema-telemetry-producers).
 
-After April 1, 2023, stable instrumentations are allowed to change the produced telemetry
+After the moratorium is lifted, stable instrumentations are allowed to change the produced telemetry
 if all the following conditions are fulfilled:
 
 - The change is part of OpenTelemetry semantic conventions and is in a released
   version of the specification.
 - The change has a corresponding [published](schemas/README.md#opentelemetry-schema)
   OpenTelemetry Schema File that describes the change.
 - The produced telemetry correctly specifies the respective Schema URL.
-
-If the change was introduced in the semantic conventions specification before
-April 1, 2023, the instrumentations must wait until April 1, 2023 before they can adopt
-the change and begin producing the changed telemetry.

specification/versioning-and-stability.md

@@ -155,6 +155,9 @@ A new, incompatible version of an integration SHOULD be released as a separate c
 
 #### Semantic Conventions Stability
 
+> **Warning**
+> There is a moratorium on relying on schema transformations for telemetry stability.
+
 Semantic conventions define a contract between the signals that instrumentation
 will provide and analysis tools that consumes the instrumentation (e.g.
 dashboards, alerts, queries, etc.).