Skip to content

Commit

Permalink
Update document statuses (open-telemetry#107)
Browse files Browse the repository at this point in the history
* Update document statuses

* Link to README section
  • Loading branch information
MrAlias authored May 25, 2021
1 parent c9b9379 commit db08bce
Show file tree
Hide file tree
Showing 6 changed files with 49 additions and 42 deletions.
43 changes: 41 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ implementation of the GDI specification is compliant if it satisfies all the
"MUST", "MUST NOT", "REQUIRED", "SHALL", and "SHALL NOT" requirements defined
in the GDI specification.

## Versioning the Specification
## Versioning and Status of the Specification

Changes to the GDI specification are versioned according to [Semantic
Versioning 2.0](https://semver.org/spec/v2.0.0.html) and described in
Expand All @@ -63,7 +63,46 @@ that implement the specification MUST specify which version they implement.
Changes to the change process itself are not currently versioned but may be
independently versioned in the future.

Additionally, the GDI specification uses following [Document Statuses](specification/document-status.md).
Specification documents (files) MAY explicitly define a "Status". If they do,
they MUST display a status immediately after the document title. When
present, the "Status" applies to the individual document only and not to the
entire specification or any other documents.

### Lifecycle status

The support guarantees and allowed changes are governed by the lifecycle of the
document. Lifecycle stages are defined in the
[versioning](./specification/versioning.md) document.

|Status |Explanation|
|--------------------|-----------|
|No explicit "Status"|Equivalent to Experimental.|
|Experimental |Breaking changes are allowed.|
|Stable |Breaking changes are no longer allowed. [1]|
|Deprecated |Changes are no longer allowed, except for editorial changes.|

- [1]: See [stability guarantees](./specification/versioning.md) for details.

### Feature freeze

In addition to the statuses above, documents may be marked as `Feature-freeze`.
These documents are not currently accepting new feature requests, to allow the
GDI specification maintainers time to focus on other areas of the specification.
Editorial changes are still accepted. Changes that address production issues
with existing features are still accepted.

Feature freeze is separate from a lifecycle status. The lifecycle represents
the support requirements for the document, feature freeze only indicates the
current focus of the specification community. The feature freeze label may be
applied to a document at any lifecycle stage. By definition, deprecated
documents have a feature freeze in place.

### Mixed

Some documents have individual sections with different statues. These documents
MUST be marked with the status `Mixed` at the top, for clarity. If a document's
status is marked as `Mixed` then it MUST define at least two different statuses
in sections that follow within the document.

## Contributions

Expand Down
2 changes: 2 additions & 0 deletions specification/configuration.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Configuration

**Status**: [Stable](../README.md#versioning-and-status-of-the-specification)

One or more configuration variables MAY be needed to properly configure GDI
repositories. Configuration of these variables MUST be supported by environment
variables and MAY be supported by additional methods. GDI repositories MUST adopt
Expand Down
40 changes: 0 additions & 40 deletions specification/document-status.md

This file was deleted.

2 changes: 2 additions & 0 deletions specification/repository.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Repository

**Status**: [Stable](../README.md#versioning-and-status-of-the-specification)

Every GDI repository MUST adhere to the following specification before
it can release a GA (`1.0.0`) release. GDI repositories MUST submit a GitHub issue
on the GDI specification using the `Repository GA approval` type. Until the
Expand Down
2 changes: 2 additions & 0 deletions specification/semantic_conventions.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Semantic Conventions

**Status**: [Stable](../README.md#versioning-and-status-of-the-specification)

This document defines the OpenTelemetry and Splunk specific standard attributes for Splunk distributions of OpenTelemetry.

## OpenTelemetry Resource Attributes
Expand Down
2 changes: 2 additions & 0 deletions specification/versioning.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,7 @@
# Versioning

**Status**: [Stable](../README.md#versioning-and-status-of-the-specification)

All GDI components MUST be versioned according to [Semantic Versioning
2.0](https://semver.org/spec/v2.0.0.html). GDI components are versioned
separately from OpenTelemetry components as Splunk-specific breaking changes
Expand Down

0 comments on commit db08bce

Please sign in to comment.