[
https://issues.apache.org/jira/browse/CALCITE-2335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16595704#comment-16595704
]
ASF GitHub Bot commented on CALCITE-2335:
-----------------------------------------
GitHub user F21 opened a pull request:
https://github.com/apache/calcite-avatica-go/pull/28
[CALCITE-2335] Set module version to v3
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Boostport/calcite-avatica-go
fix-go-module-version
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/calcite-avatica-go/pull/28.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #28
----
commit eb4d11c77d462c59c4376381972b4b86aba5037a
Author: Francis Chuang <francischuang@...>
Date: 2018-08-28T23:06:16Z
[CALCITE-2335] Set module version to v3
----
> Switch to vgo for dependency management
> ---------------------------------------
>
> Key: CALCITE-2335
> URL: https://issues.apache.org/jira/browse/CALCITE-2335
> Project: Calcite
> Issue Type: Task
> Components: avatica-go
> Reporter: Francis Chuang
> Assignee: Francis Chuang
> Priority: Major
> Fix For: avatica-go-3.1.0
>
>
> The proposal for vgo has been accepted:
> [https://research.swtch.com/vgo-accepted]
> vgo aims to replace dep for dependency management in Go.
> TLDR; vgo will be part of the Go tool chain in Go 1.11 (July 31 2018) on an
> experimental basis. Official production-ready status will be in Go 1.12
> (January 2019).
> We should remove dep and move to vgo when Go 1.11 is released so that we can
> work out any idiosyncrasies before Go 1.12.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
