[ https://issues.apache.org/jira/browse/CALCITE-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16453421#comment-16453421 ]
ASF GitHub Bot commented on CALCITE-1937: ----------------------------------------- Github user risdenk commented on a diff in the pull request: https://github.com/apache/calcite-avatica/pull/43#discussion_r184259467 --- Diff: site/news/avatica-go-releases/index.html --- @@ -0,0 +1,28 @@ +--- +layout: news +title: Avatica Go Releases +permalink: /news/avatica-go-releases/ +author: all +--- +{% comment %} --- End diff -- Missing `<!--` and `-->` before and after the license comment? Saw this on the other files in this PR. > Web site for Avatica Go > ----------------------- > > Key: CALCITE-1937 > URL: https://issues.apache.org/jira/browse/CALCITE-1937 > Project: Calcite > Issue Type: Bug > Components: avatica-go > Reporter: Julian Hyde > Assignee: Francis Chuang > Priority: Major > > Create a web site for calcite-avatica-go. > How about this: > * At run time, the pages should appear under http://calcite.apache.org/avatica > * The pages should be source-controlled under calcite-avatica-go/site, in > markdown format (same as calcite and avatica), and generated into svn using > similar trickery to calcite and avatica. > * Reduce the amount of content in > https://github.com/apache/calcite-avatica-go/blob/master/README.md. The > "documentation" stuff should move to under http://calcite.apache.org/avatica. > So the page will be mainly a re-direct to the Apache home page. Similar to > https://github.com/apache/calcite-avatica/blob/master/README.md, in fact. > * Add a go_history.md file. > Should avatica-go appear on http://calcite.apache.org/avatica/downloads, or > should it have its own download page? I think it probably the former. -- This message was sent by Atlassian JIRA (v7.6.3#76005)