[jira] [Comment Edited] (CALCITE-6017) The content of github link about the released versions in history doc is empty
[
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768676#comment-17768676
]
Ran Tao edited comment on CALCITE-6017 at 9/25/23 1:49 PM:
---
I think I got the reason from
[https://github.com/orgs/community/discussions/6396]. The early behavior of
GitHub was that if there was no release, the tag would be displayed, but after
2021.10, these two functions were decoupled, so the release is empty unless the
release is explicitly specified (however calcite not use GitHub to publish
release artifacts).
we can see from end of 2021, there is empty.
[https://web.archive.org/web/20211219215203/https://github.com/apache/calcite/releases]
Considering that very early calcite release pages in GitHub are tags actually.
e.g. [releases as of 2021-03-06 per Wayback
machine|https://web.archive.org/web/20210306054735/https://github.com/apache/calcite/releases].
IMHO, we can use tags explicitly to replace this link either.
[~julianhyde] [~shenlang] any suggestions? what do you think?
was (Author: lemonjing):
I think I got the reason from
[https://github.com/orgs/community/discussions/6396]. The early behavior of
GitHub was that if there was no release, the tag would be displayed, but after
2021.10, these two functions were decoupled, so the release is empty unless the
release is explicitly specified (however calcite not use GitHub to publish
release artifacts).
we can see from end of 2021, there is empty.
[https://web.archive.org/web/20211219215203/https://github.com/apache/calcite/releases]
Considering that very early calcite release pages in GitHub are tags actually.
e.g. [releases as of 2021-03-06 per Wayback
machine|https://web.archive.org/web/20210306054735/https://github.com/apache/calcite/releases].
IMHO, we can use tags explicitly to replace this link either.
[~julianhyde] hi, Julian, what do you think?
> The content of github link about the released versions in history doc is empty
> --
>
> Key: CALCITE-6017
> URL: https://issues.apache.org/jira/browse/CALCITE-6017
> Project: Calcite
> Issue Type: Improvement
>Reporter: Ran Tao
>Assignee: Ran Tao
>Priority: Minor
> Labels: doc
> Attachments: image-2023-09-21-16-03-16-132.png,
> image-2023-09-21-16-04-00-579.png, image-2023-09-21-16-04-54-398.png
>
>
> In calcite history page, we have a description:
> {noformat}
> For a full list of releases, see
> https://github.com/apache/calcite/releases;>github.
> {noformat}
> however, there is nothing on this page, because calcite not use github to
> manage the released versions. So this description may seem a bit strange to
> end users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CALCITE-6017) The content of github link about the released versions in history doc is empty
[
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768676#comment-17768676
]
Ran Tao edited comment on CALCITE-6017 at 9/25/23 12:52 PM:
I think I got the reason from
[https://github.com/orgs/community/discussions/6396]. The early behavior of
GitHub was that if there was no release, the tag would be displayed, but after
2021.10, these two functions were decoupled, so the release is empty unless the
release is explicitly specified (however calcite not use GitHub to publish
release artifacts).
we can see from end of 2021, there is empty.
[https://web.archive.org/web/20211219215203/https://github.com/apache/calcite/releases]
Considering that very early calcite release pages in GitHub are tags actually.
e.g. [releases as of 2021-03-06 per Wayback
machine|https://web.archive.org/web/20210306054735/https://github.com/apache/calcite/releases].
IMHO, we can use tags explicitly to replace this link either.
[~julianhyde] hi, Julian, what do you think?
was (Author: lemonjing):
I think I got the reason from
https://github.com/orgs/community/discussions/6396. The early behavior of
GitHub was that if there was no release, the tag would be displayed, but after
2021.10, these two functions were decoupled, so the release is empty unless the
release is displayed (however calcite not use GitHub to publish release
artifacts).
we can see from end of 2021, there is empty.
[https://web.archive.org/web/20211219215203/https://github.com/apache/calcite/releases]
Considering that very early calcite release pages in GitHub are tags actually.
e.g. [releases as of 2021-03-06 per Wayback
machine|https://web.archive.org/web/20210306054735/https://github.com/apache/calcite/releases].
IMHO, we can use tags explicitly to replace this link either.
[~julianhyde] hi, Julian, what do you think?
> The content of github link about the released versions in history doc is empty
> --
>
> Key: CALCITE-6017
> URL: https://issues.apache.org/jira/browse/CALCITE-6017
> Project: Calcite
> Issue Type: Improvement
>Reporter: Ran Tao
>Priority: Minor
> Labels: doc
> Attachments: image-2023-09-21-16-03-16-132.png,
> image-2023-09-21-16-04-00-579.png, image-2023-09-21-16-04-54-398.png
>
>
> In calcite history page, we have a description:
> {noformat}
> For a full list of releases, see
> https://github.com/apache/calcite/releases;>github.
> {noformat}
> however, there is nothing on this page, because calcite not use github to
> manage the released versions. So this description may seem a bit strange to
> end users.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CALCITE-6017) The content of github link about the released versions in history doc is empty
[ https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767175#comment-17767175 ] Ran Tao edited comment on CALCITE-6017 at 9/20/23 3:55 PM: --- [~shenlang] we have a description in history.md to let user visit github released link, however the content of this link is empty, without any calcite released versions. was (Author: lemonjing): [~shenlang] we have a description in history.md to let user visit github released link, however this link is empty, without any calcite released versions. > The content of github link about the released versions in history doc is empty > -- > > Key: CALCITE-6017 > URL: https://issues.apache.org/jira/browse/CALCITE-6017 > Project: Calcite > Issue Type: Improvement >Reporter: Ran Tao >Priority: Minor > Labels: doc > > In calcite history page, we have a description: > > For a full list of releases, see > https://github.com/apache/calcite/releases;>github. > however, there is nothing on this page, because calcite not use github to > manage the released versions. So this description may seem a bit strange to > end users. -- This message was sent by Atlassian Jira (v8.20.10#820010)
