You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2016/03/08 23:49:40 UTC

[jira] [Resolved] (CALCITE-1077) Separate Avatica from "core" Calcite build

     [ https://issues.apache.org/jira/browse/CALCITE-1077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser resolved CALCITE-1077.
---------------------------------
    Resolution: Fixed

Closing due to the completion of all sub-tasks.

> Separate Avatica from "core" Calcite build
> ------------------------------------------
>
>                 Key: CALCITE-1077
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1077
>             Project: Calcite
>          Issue Type: Task
>          Components: avatica
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.7.0
>
>
> Uber-JIRA-issue for tracking the separation of Avatica from the rest of the Calcite build.
> Long term, Avatica can be a standalone project, but we're not there yet in terms of governance (enough people intimately involved). One thing we can do now is to separate Avatica from Calcite and begin "getting them used to" not being next to one another.
> DISCUSS thread: https://mail-archives.apache.org/mod_mbox/calcite-dev/201601.mbox/%3C56ABCCFF.3010205%40gmail.com%3E



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)