Refactor versioning docs (#328)

Author: pellared

README.md

@@ -85,6 +85,14 @@ document. Lifecycle stages are defined in the
 
 - [1]: See [stability guarantees](./specification/versioning.md) for details.
 
+## Experimental
+
+Everything in the specification starts as `Experimental`.
+
+`Experimental` sections SHOULD NOT be expected to be feature-complete.
+In some cases, the experiment MAY be discarded and removed entirely.
+Long-term dependencies SHOULD NOT be taken against experimental sections.
+
 ### Feature freeze
 
 In addition to the statuses above, documents may be marked as `Feature-freeze`.

specification/versioning.md

@@ -3,26 +3,18 @@
 **Status**: [Stable](../README.md#versioning-and-status-of-the-specification)
 
 All GDI repositories MUST be versioned according to [Semantic Versioning
-2.0](https://semver.org/spec/v2.0.0.html). GDI repositories are versioned
-separately from OpenTelemetry repositories as Splunk-specific breaking changes
-MAY be introduced. GDI repositories MUST indicate what version of OpenTelemetry
+2.0](https://semver.org/spec/v2.0.0.html) using the syntax idiomatic to their
+language.
+
+GDI repositories are versioned separately from OpenTelemetry repositories as
+Splunk-specific breaking changes MAY be introduced.
+GDI repositories MUST indicate what version of OpenTelemetry
 repositories they are based on through release notes and SHOULD indicate through
 logging. Additional version number constraints can be found in the sections
 below.
 
 ## Experimental
 
-Everything in the specification starts as experimental, which covers alpha,
-beta, and release candidate versions. Version numbers for releases MUST be less
-than `1.0.0` while experimental. The minor version number SHOULD be increased
-when significant or breaking changes are introduced.
-
-While any section in the specification is experimental, breaking changes and
-performance issues MAY occur. Sections SHOULD NOT be expected to be
-feature-complete. In some cases, the experiment MAY be discarded and removed
-entirely. Long-term dependencies SHOULD NOT be taken against experimental
-sections.
-
 GDI repositories MAY consist of one or more components. GDI repositories MUST be
 designed in a manner that allows experimental components to be created without
 breaking the stability guarantees of existing components. GDI repositories MUST NOT
@@ -41,9 +33,8 @@ configuration variable to enable, and MUST clearly be marked as experimental.
 
 ## Stable
 
-The initial stable release version number for GDI repositories MUST be `1.0.0` and
-follow Semantic Versioning 2.0 for all subsequent releases. Once an
-experimental component has gone through rigorous beta testing, it MAY
+The initial stable release version number for GDI repositories MUST be `1.0.0`.
+Once an experimental component has gone through rigorous beta testing, it MAY
 transition to stable. Long-term dependencies MAY now be taken against this
 component. When a new stable component is introduced to a GDI repository with an
 existing stable release, the `MINOR` version number MUST be incremented and the