[jira] [Commented] (CALCITE-1717) Move Avatica into its own git repository

["Josh Elser (JIRA)" <ji...@apache.org>]

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

Josh Elser commented on CALCITE-1717:
-------------------------------------

Here are the details of what I think we would need to do and what would fundamentally change in our current workflow:

* Push {{HEAD}} from calcite.git to calcite-avatica.git
* {{git rm}} all of the children of calcite-avatica.git except for {{avatica}}
* {{git mv avatica/* .}}
* {{git rm avatica}} from calcite.git

* Update Avatica website to deploy into it's own {{_site/target}} instead of {{../_site/target}}
* Create news article for Avatica and Calcite websites (let people know -- in addition to an email)

I think that's it.

> Move Avatica into its own git repository
> ----------------------------------------
>
>                 Key: CALCITE-1717
>                 URL: https://issues.apache.org/jira/browse/CALCITE-1717
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> Move Avatica into its own git repository.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)