[jira] [Commented] (CALCITE-6017) The content of github link about the released versions in history doc is empty

2023-09-26 Thread Ran Tao (Jira)


[ 
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17769022#comment-17769022
 ] 

Ran Tao commented on CALCITE-6017:
--

thanks for feedback. then i will open a PR to change this link.

> 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] [Commented] (CALCITE-6017) The content of github link about the released versions in history doc is empty

2023-09-25 Thread Julian Hyde (Jira)


[ 
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768815#comment-17768815
 ] 

Julian Hyde commented on CALCITE-6017:
--

I agree with [~rubenql]. The tags will have a few extra entries - the release 
candidates, including the failed ones - but that information may also be useful 
to the reader.

[~taoran], Thank you for taking the time to research and document the cause of 
this problem.

> 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] [Commented] (CALCITE-6017) The content of github link about the released versions in history doc is empty

2023-09-25 Thread Ruben Q L (Jira)


[ 
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768725#comment-17768725
 ] 

Ruben Q L commented on CALCITE-6017:


Thanks for digging into this, [~taoran]. Looking at your analysis, IMHO 
replacing the link with "tags" seems a reasonable way to fix this issue.

> 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] [Commented] (CALCITE-6017) The content of github link about the released versions in history doc is empty

2023-09-25 Thread Ran Tao (Jira)


[ 
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17768676#comment-17768676
 ] 

Ran Tao commented on CALCITE-6017:
--

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] [Commented] (CALCITE-6017) The content of github link about the released versions in history doc is empty

2023-09-21 Thread Julian Hyde (Jira)


[ 
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767443#comment-17767443
 ] 

Julian Hyde commented on CALCITE-6017:
--

What happened on GitHub so that the list of releases is now empty? That is what 
needs to be fixed.

> 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] [Commented] (CALCITE-6017) The content of github link about the released versions in history doc is empty

2023-09-21 Thread Ran Tao (Jira)


[ 
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767441#comment-17767441
 ] 

Ran Tao commented on CALCITE-6017:
--

yes, the old archived link is correct. however, if we call 
[https://github.com/apache/calcite/releases] directly, the page is nothing 
unless we switch to tags.


!image-2023-09-21-16-04-54-398.png|width=485,height=186!
!image-2023-09-21-16-04-00-579.png|width=479,height=280!

> 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] [Commented] (CALCITE-6017) The content of github link about the released versions in history doc is empty

2023-09-20 Thread Julian Hyde (Jira)


[ 
https://issues.apache.org/jira/browse/CALCITE-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17767249#comment-17767249
 ] 

Julian Hyde commented on CALCITE-6017:
--

The page used to contain releases, e.g. [releases as of 2021-03-06 per Wayback 
machine|https://web.archive.org/web/20210306054735/https://github.com/apache/calcite/releases].

What broke?

> 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:
> {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)