[
https://issues.apache.org/jira/browse/CALCITE-2333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493141#comment-16493141
]
Julian Hyde commented on CALCITE-2333:
--------------------------------------
+1
The {{has_zip: true}} property would work, or you could add some logic to
{{site/community/index.md}} that compares the release date to 2018-06-01,
similar to what we did for .sha256 vs .md5 digests.
> Stop releasing ZIPs
> -------------------
>
> Key: CALCITE-2333
> URL: https://issues.apache.org/jira/browse/CALCITE-2333
> Project: Calcite
> Issue Type: Task
> Components: avatica, avatica-go, core
> Reporter: Francis Chuang
> Assignee: Francis Chuang
> Priority: Trivial
>
> There was some discussion on the mailing list regarding releasing our source
> in just 1 format.
> See
> https://mail-archives.apache.org/mod_mbox/calcite-dev/201804.mbox/%3CD60019E6-FC62-4C24-B2F0-5278E51E5626%40apache.org%3E
> There is some consensus around just releasing a tar.gz. I think this is a
> good idea and is something we should aim for, for the Calcite 1.17 and
> Avatica 1.17 releases.
> The following changes will be needed:
> * Update build script for avatica-go.
> * Update maven config for avatica.
> * Update calcite config for calcite.
> We will need to update the website to deal the zip files not existing. My
> proposal is that we edit the old release posts to include a `has_zip: true`
> property. For the old releases, the website should render a link to the zip.
> For the new releases, we do not need to do anything.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
