Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Declare freeze of Trace Specification 1.0 #1120

Closed
tigrannajaryan opened this issue Oct 20, 2020 · 2 comments
Closed

Declare freeze of Trace Specification 1.0 #1120

tigrannajaryan opened this issue Oct 20, 2020 · 2 comments
Assignees
@tigrannajaryan
Labels
release:required-for-ga Must be resolved before GA release, or nice to have before GA spec:trace Related to the specification/trace directory

Comments

@tigrannajaryan
Copy link
Member

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).
@tigrannajaryan tigrannajaryan added the spec:trace Related to the specification/trace directory label Oct 20, 2020
@tigrannajaryan tigrannajaryan self-assigned this Oct 20, 2020
tigrannajaryan pushed a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Oct 20, 2020
Declare freeze of Trace Specification 1.0
2416532 
We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry#1120
@tigrannajaryan tigrannajaryan mentioned this issue Oct 20, 2020
Merged
@Oberon00
Copy link
Member

Oberon00 commented Oct 21, 2020 •
edited
Loading

May I plug one issue that I think should be reconsidered to be required-for-ga tracing: #1060. I think we are missing specification for when to generate span IDs for unsampled spans. One argument for this being important is on the associated PR: #998 (comment)

@Oberon00 Oberon00 added the release:required-for-ga Must be resolved before GA release, or nice to have before GA label Oct 21, 2020
@andrewhsu
Copy link
Member

Some action items I see that are desirable for this freeze to remain consistent with previous milestone and releases:

  • git tag and push to repo
  • update github milestone to represent what has gone into this release
  • write changelog for github release

I'm willing to help out on these items.

tigrannajaryan pushed a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Nov 3, 2020
Declare freeze of Trace Specification 1.0
ef8ed78 
We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry#1120
tigrannajaryan pushed a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Nov 9, 2020
@tigrannajaryan
Declare freeze of Trace Specification 1.0
31b4ac2 
We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry#1120
tigrannajaryan pushed a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Nov 12, 2020
@tigrannajaryan
Declare freeze of Trace Specification 1.0
6fb84c8 
We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry#1120
tigrannajaryan pushed a commit to tigrannajaryan/opentelemetry-specification that referenced this issue Nov 16, 2020
@tigrannajaryan
Declare freeze of Trace Specification 1.0
0b71f05 
We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry#1120
jack-berg pushed a commit to jack-berg/semantic-conventions that referenced this issue Nov 7, 2023
@tigrannajaryan @jack-berg
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
c96b2f6 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
AlexanderWert pushed a commit to jack-berg/semantic-conventions that referenced this issue Nov 10, 2023
@tigrannajaryan @AlexanderWert
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
bccc684 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
jack-berg pushed a commit to jack-berg/semantic-conventions that referenced this issue Nov 16, 2023
@tigrannajaryan @jack-berg
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
267cdfb 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
jack-berg pushed a commit to jack-berg/semantic-conventions that referenced this issue Nov 16, 2023
@tigrannajaryan @jack-berg
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
49eed2c 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
jsuereth pushed a commit to jack-berg/semantic-conventions that referenced this issue Nov 16, 2023
@tigrannajaryan @jsuereth
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
3cc7e8a 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
jsuereth pushed a commit to jack-berg/semantic-conventions that referenced this issue Nov 16, 2023
@tigrannajaryan @jsuereth
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
0731215 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
jsuereth pushed a commit to open-telemetry/semantic-conventions that referenced this issue Nov 16, 2023
@tigrannajaryan @jsuereth
Declare freeze of Trace API Specification 1.0 (#1121)
e8587ba 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
jsuereth pushed a commit to open-telemetry/semantic-conventions that referenced this issue Nov 16, 2023
@tigrannajaryan @jsuereth
Declare freeze of Trace API Specification 1.0 (#1121)
4c23074 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
joaopgrassi pushed a commit to dynatrace-oss-contrib/semantic-conventions that referenced this issue Jan 10, 2024
@tigrannajaryan
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
0c580d7 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
joaopgrassi pushed a commit to dynatrace-oss-contrib/semantic-conventions that referenced this issue Jan 10, 2024
@tigrannajaryan
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
49b70ba 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
pyohannes pushed a commit to pyohannes/semantic-conventions that referenced this issue Jan 17, 2024
@tigrannajaryan @pyohannes
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
ce3279a 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
pyohannes pushed a commit to pyohannes/semantic-conventions that referenced this issue Jan 17, 2024
@tigrannajaryan @pyohannes
Declare freeze of Trace API Specification 1.0 (open-telemetry#1121)
81f9a09 
* Declare freeze of Trace Specification 1.0

We want to freeze Trace specification 1.0 so that we no longer accept substantial changes (unless a fundamental problem is found in the spec).

Resolves open-telemetry/opentelemetry-specification#1120
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tigrannajaryan tigrannajaryan

Labels
release:required-for-ga Must be resolved before GA release, or nice to have before GA spec:trace Related to the specification/trace directory
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@andrewhsu @Oberon00 @tigrannajaryan