[DO NOT MERGE] [Trace] Deprecate Record Exception API in favor of using Logs API

CHANGELOG.md

@@ -11,6 +11,9 @@ release.
 
 ### Traces
 
+- Deprecate Record Exception API in favor of using Logs.
+  ([#4825](https://github.com/open-telemetry/opentelemetry-specification/pull/4825))
+
 ### Metrics
 
 - Stabilize part of `Enabled` SDK for synchronous instruments.

specification/trace/api.md

@@ -683,6 +683,8 @@ in the scope of this requirement and recommendation.
 
 #### Record Exception
 
+**Status**: [Deprecated](../document-status.md)
+
 To facilitate recording an exception languages SHOULD provide a
 `RecordException` method if the language uses exceptions.
 This is a specialized variant of [`AddEvent`](#add-events),

specification/trace/exceptions.md

@@ -1,6 +1,8 @@
 # Exceptions
 
-**Status**: [Stable](../document-status.md), Unless otherwise specified.
+**Status**: [Deprecated](../document-status.md), follow the
+[semantic conventions for recording exceptions](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/recording-errors.md#recording-exceptions)
+instead.
 
 This document defines how to record exceptions and their attributes.
 
@@ -19,8 +21,6 @@ to be set to ERROR.
 
 The name of the event MUST be `"exception"`.
 
-**Status**: [Development](../document-status.md) - Refer to the [Recording Errors](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/general/recording-errors.md) document for the details on how to report errors across signals.
-
 A typical template for an auto-instrumentation implementing this semantic convention
 using an [API-provided `recordException` method](api.md#record-exception)
 could look like this (pseudo-Java):