-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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.
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
Status page > Latest releases: not all links are to the latest release #905
Closed
10 tasks done
Tracked by
#925
Comments
sgtm |
I believe if we remove this then we can nix the script that pulls release info as well and remove some cruft from the build. |
This was referenced Nov 16, 2021
Closed
chalin
added a commit
to chalin/opentelemetry-java
that referenced
this issue
Nov 16, 2021
This was referenced Nov 16, 2021
chalin
added a commit
to chalin/opentelemetry-go
that referenced
this issue
Nov 16, 2021
chalin
added a commit
to chalin/opentelemetry-php
that referenced
this issue
Nov 16, 2021
chalin
added a commit
to chalin/opentelemetry-python
that referenced
this issue
Nov 16, 2021
chalin
added a commit
to chalin/opentelemetry-ruby
that referenced
this issue
Nov 16, 2021
MrAlias
added a commit
to open-telemetry/opentelemetry-go
that referenced
this issue
Nov 16, 2021
Contributes to open-telemetry/opentelemetry.io#905. /cc @austinlparker Co-authored-by: Tyler Yahn <[email protected]>
jkwatson
pushed a commit
to open-telemetry/opentelemetry-java
that referenced
this issue
Nov 16, 2021
fbogsany
pushed a commit
to open-telemetry/opentelemetry-ruby
that referenced
this issue
Nov 16, 2021
bobstrecansky
pushed a commit
to open-telemetry/opentelemetry-php
that referenced
this issue
Nov 16, 2021
ocelotl
pushed a commit
to open-telemetry/opentelemetry-python
that referenced
this issue
Nov 17, 2021
shbieng
added a commit
to shbieng/opentelemetry-go
that referenced
this issue
Aug 26, 2022
Contributes to open-telemetry/opentelemetry.io#905. /cc @austinlparker Co-authored-by: Tyler Yahn <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary: I'd like to suggest that we do away with the "Latest release" section of the status page because it isn't up-to-date, and interested readers can visit the SIG's landing page for a link to the latest release. WDYT @austinlparker?
Work items:
Details:
The releases section of the status page now looks like this (as of 2021/11/11):
Looking at this a bit more closely I'm noticing that some links refer to a version that is not the latest release:
The proper release info is given in the SIG's landing page, https://opentelemetry.io/docs/ruby/.
The proper release info is given in the SIG's landing page, https://opentelemetry.io/docs/erlang/.
Given that the landing pages for most language SIGs contain a link to the SIG's release page, I'd like to suggest that we do away with the "Latest release" section of the status page. WDYT @austinlparker? If you agree, I'll ensure that each SIG's landing page does indeed contain a link to releases.
The text was updated successfully, but these errors were encountered: