[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438859#comment-16438859 ] Julian Hyde commented on CALCITE-1938: -- I'm not very expert in travis. In any case, I do not think that travis is a blocker for the release. Let's get the release out first. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang >Priority: Major > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avatica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438814#comment-16438814 ] Kevin Risden commented on CALCITE-1938: --- [Francis Chuang|applewebdata://A306AA86-585D-48FC-80D1-42FFD251E9C6/jira/secure/ViewProfile.jspa?name=francischuang] - Looks like INFRA-16380 was completed. I opened CALCITE-2258 and created a PR for it. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang >Priority: Major > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avatica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438556#comment-16438556 ] Francis Chuang commented on CALCITE-1938: - Thanks [~risdenk]. INFRA-16360 opened to track travis integration. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang >Priority: Major > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avatica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16438465#comment-16438465 ] Kevin Risden commented on CALCITE-1938: --- [~francischuang] - I think this would be a ticket to INFRA. Here are two examples: INFRA-13792 and INFRA-11616 > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang >Priority: Major > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avatica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435007#comment-16435007 ] Francis Chuang commented on CALCITE-1938: - [~julianhyde], would it be possible to set up travis for the calcite-avatica-go repo? > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang >Priority: Major > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avatica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16179164#comment-16179164 ] Josh Elser commented on CALCITE-1938: - No worries on timing, Francis. We all get busy :) bq. HSQLDB does not seem to be very stable What do you mean? It's worked fine for how I've used it. If you're having specific troubles, Julian or myself can likely give a recommendation. We use hsqldb quite extensively in tests already -- I'd be surprised if it has some major limitation. bq. What is the Apache foundation's stance on spinning up an instance of MySQL for tests MySQL and MariaDB are GPL licensed. So, we would not be able to bundle them in any release. I believe we would be allowed to have test-only automation which installs/runs them, but I'm not positive. [~julianhyde] might remember more what policy states off the top of his head (else, I'll have to go digging). > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[
https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16131434#comment-16131434
]
Francis Chuang commented on CALCITE-1938:
-
{quote}
Is Gitbox a requirement for using Travis/Wercker? Calcite and Avatica already
use Travis..
{quote}
No it's not. However, I believe enabling Gitbox turns the Github repo into the
"source of truth". Currently, you'd need Jenkis for CI to run tests on the
master branch of the ASF repo. However, Jenkins is not able to run tests for
PRs on Github. However, if Github becomes the source of truth via Gitbox, then
we could just use Travis/Wercker, etc to run tests on Github's master branch
and any PRs.
> First Apache release for Avatica Go
> ---
>
> Key: CALCITE-1938
> URL: https://issues.apache.org/jira/browse/CALCITE-1938
> Project: Calcite
> Issue Type: Bug
> Components: avatica-go
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>
> Make a release for Avatica Go.
> Release number is TBD.
> This will be the first Apache release for Avacica Go, so expect more
> diligence / issues than usual.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130350#comment-16130350 ] Josh Elser commented on CALCITE-1938: - bq. This will allow merging PRs on Github IMO, I don't see the value in setting up Gitbox just to be able to click a button to merge a PR. We don't use Github Issues/Labels which, I believe, is the primary reason this functionality came about. bq. perhaps we can just use Travis or Wercker for CI and forego having to use jenkins on ASF infra. Is Gitbox a requirement for using Travis/Wercker? Calcite and Avatica already use Travis.. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130281#comment-16130281 ] Francis Chuang commented on CALCITE-1938: - Just a quick update on what I've been working on. I've added an environment variable called AVATICA_FLAVOR for running tests. You'd set it to HSQLDB to run tests against the calcite-avatica-hsqldb image and PHOENIX to run tests against phoenix. These tests can be run in parallel using a build matrix on Travis or pipelines in Wercker. I've ported most of the Phoenix tests over but there are a few failing that I haven't had time to investigate. There are a few where I believe relates to bugs in the hsqldb image and JIRAs have been opened for them. How do you guys feel about using gitbox (https://gitbox.apache.org) for the calcite-avatica-go repo? This will allow merging PRs on Github and perhaps we can just use Travis or Wercker for CI and forego having to use jenkins on ASF infra. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[
https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125192#comment-16125192
]
Francis Chuang commented on CALCITE-1938:
-
{quote}
Couldn't something be done to figure out the flavor of database and what it
supports? I think we have driver information already sent back from the server.
Maybe it's as simple as returning that back? Syntax shouldn't matter for the
driver itself, just the sql provided, no?
{quote}
>From the RpcMetadata message, I only see that the server_address is returned.
>However, I don't think this is a blocker, because if we have a test matrix
>like in travis-ci, we can execute both the Phoenix and HSQLdb tests separately
>by switching against a environment variable.
The driver does not care about the syntax itself, however in the tests, we
execute statements against Phoenix using `UPSERT ...`. Since HSQLdb uses
insert/update, we would need to rewrite the SQL statements in the appropriate
syntax. There is also a test that inserts into a table using all the various
Phoenix data types and selects them to see that the data is being saved and
read correctly, and we'd need a seperate one for HSQLdb.
These are not insurmountable challenges. Since all the integration tests are in
driver_test.go, we could turn that into driver_phoenix_test.go and
driver_hsqldb_test.go and have the different flavors run depending on what the
environment variable AVATICA_FLAVOR is set to.
{quote}
Anyways, I don't think it's a good use of our time to try to deploy a full
hbase installation on the ASF infra. It tends to be over-taxed already – a
minimal testing environment is the best plan of action.
{quote}
I agree that it's not productive to set up an HBase install, but if we are
using jenkins, is it possible to use a docker image as a service? If so, my
hbase-phoenix-all-in-one image spins up a container that has hbase-standalone,
phoenix, pqs and tephra enabled. This should require about the same effort as
testing against the avatica-hsqldb image.
> First Apache release for Avatica Go
> ---
>
> Key: CALCITE-1938
> URL: https://issues.apache.org/jira/browse/CALCITE-1938
> Project: Calcite
> Issue Type: Bug
> Components: avatica-go
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>
> Make a release for Avatica Go.
> Release number is TBD.
> This will be the first Apache release for Avacica Go, so expect more
> diligence / issues than usual.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125183#comment-16125183 ] Josh Elser commented on CALCITE-1938: - bq. I'd definitely keep the tests running against Phoenix at the very least since the driver advertises Phoenix support Support for Phoenix's use of Avatica should be secondary to making sure that it works against Avatica "proper". bq. It's possible to duplicate the tests and run them twice, once on Phoenix and once on avatica + hsqldb, but I am wondering if the payoff is worth it (tests would probably take twice as long to run). Couldn't something be done to figure out the flavor of database and what it supports? I think we have driver information already sent back from the server. Maybe it's as simple as returning that back? Syntax shouldn't matter for the driver itself, just the sql provided, no? Anyways, I don't think it's a good use of our time to try to deploy a full hbase installation on the ASF infra. It tends to be over-taxed already -- a minimal testing environment is the best plan of action. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125177#comment-16125177 ] Francis Chuang commented on CALCITE-1938: - There are some "traditional" unit tests to test parsing the dsn when setting up the db connection: https://github.com/apache/calcite-avatica-go/blob/master/dsn_test.go But other than that, since this is a database/sql it makes sense to test everything else against a real database, rather than try and mock the database. Testing against the calcite-avatica image is possible, however, I chose Phoenix when the driver was first written because: - I am using the driver against Phoenix in my projects. - The avatica + hsqldb image did not exist back then. - I needed to test the Phoenix error codes. I'd definitely keep the tests running against Phoenix at the very least since the driver advertises Phoenix support. It should be possible to add support for testing against avatica + hsqldb, however, from what I can see, Phoenix is not using Calcite yet, so the SQL syntax is sightly different (UPSERT vs INSERT/Update) and the data types supported are different. It's possible to duplicate the tests and run them twice, once on Phoenix and once on avatica + hsqldb, but I am wondering if the payoff is worth it (tests would probably take twice as long to run). > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125127#comment-16125127 ] Josh Elser commented on CALCITE-1938: - bq. The tests are integration tests, so you'd need to have an instance of Phoenix and PQS available Ok.. the README needs to be updated then. It's a bit misleading at this point. Do you have any "traditional" unit tests on the horizon? How much work do you think it would be to use https://hub.docker.com/r/apache/calcite-avatica/ instead (avatica + hsqldb)? Reducing the scope of what is required to run tests would be great. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125117#comment-16125117 ] Francis Chuang commented on CALCITE-1938: - [~elserj] The tests are integration test, so you'd need to have an instance of phoenix and PQS available. In my tests, I use my HBase-Phoenix docker image with transactions and PSQ enabled: https://github.com/Boostport/hbase-phoenix-all-in-one Once this is done, you need to set the AVATICA_HOST environment variable to point to PQS. The tests do take a while to run (because creating and deleting schemas and tables can be a bit slow), but if the PQS is not available after 5 minutes, the tests should timeout and fail. You can check out how the tests are set up and executed on Wercker here: https://github.com/apache/calcite-avatica-go/blob/master/wercker.yml > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[
https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16125103#comment-16125103
]
Josh Elser commented on CALCITE-1938:
-
{noformat}
$ mkdir -p ~/go/src/github.com/apache
$ git clone https://git-wip-us.apache.org/repos/asf/calcite-avatica-go.git
$ cd calcite-avatica-go
$ dep ensure
$ go test $(go list ./... | grep -v vendor)
{noformat}
The {{go test}} command just seems to hang and not do anything. I can't seem to
find any sort of option for more verbosity either. Thoughts, [~francischuang]?
> First Apache release for Avatica Go
> ---
>
> Key: CALCITE-1938
> URL: https://issues.apache.org/jira/browse/CALCITE-1938
> Project: Calcite
> Issue Type: Bug
> Components: avatica-go
>Reporter: Julian Hyde
>Assignee: Francis Chuang
>
> Make a release for Avatica Go.
> Release number is TBD.
> This will be the first Apache release for Avacica Go, so expect more
> diligence / issues than usual.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124449#comment-16124449 ] Francis Chuang commented on CALCITE-1938: - For Go libraries, building a binary out of a library isn't very useful. In Go, there is the concept of the GOPATH. It is an environment variable pointing to a folder where you store and work on your Go projects. GOPATH should contain the src/, pkg/ and bin/ folders. Projects are placed in `src/`, for example `src/github.com/apache/calcite-avatica-go`. Executables are placed in bin, and they are built by running `go install` in your project. Under `pkg/`, you'd find the package binaries. They are intermediate objects that are cached by the go tool. For example, if I run `go install` in `src/github.com/some-org/some-project` to build an executable, and that project imports a certain version of calcite-avatica-go, the calcite-avatica-go dependency will be built as `src/github.com/apache/calcite-avatica-go.a`. In Go, libraries are not shipped and built as binaries are they are not very useful. The built binaries under the pkg/ folder are only temporary objects cached by Go to improve build performance and they should be re-built during the compilation of an executable. The standard workflow is to use the dep tool or some third party dependency management tool. It will check out the source into the project's vendor directory, and if `go install` or `go build` is executed, it will build the final binary. >From my understand of maven and comparing with Go: - Go does not need the clean step, as running tests or building does not create temporary or binaries in the source tree. - To test, we run `go test $(go list ./... | grep -v /vendor/)`. All this does is tell the go tool to traverse the project for test files and execute them, but exclude anything in the vendor/ folder because they contain the source of our dependencies. - Go install is not meaningful for a library. If the project produced an executable, then `go install` can be used to build and place the binary into GOPATH/bin. However, since calcite-avatica-go is a library, and there is no main package in the code, it is not meaningful to build a binary. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16124435#comment-16124435 ] Julian Hyde commented on CALCITE-1938: -- As part of the release, we need developer instructions. Under Apache, it's important that when you download a source distribution, you can build that actual source code. Not the source code that is in github etc. Maybe I misunderstand the current developer instructions in README.md, but it seems to be building code that is in a particular github repo (or referencing binaries that have been previously built from that repo). For the purposes of an Apache release, we need the equivalent of 'mvn clean test install', and that needs to be fairly prominent in the README that comes with the release. Is that possible? > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16123753#comment-16123753 ] Josh Elser commented on CALCITE-1938: - bq. Josh Elser might be better able to set up CI. He did it for Calcite and Avatica. Would you mind taking this on, Josh? Yup! Not a problem. Will try to do it this weekend. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122851#comment-16122851 ] Francis Chuang commented on CALCITE-1938: - Yea, I think 2.2.0 would be good for the first Apache release. That makes sense. > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122850#comment-16122850 ] Julian Hyde commented on CALCITE-1938: -- [~elserj] might be better able to set up CI. He did it for Calcite and Avatica. Would you mind taking this on, Josh? > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122835#comment-16122835 ] Julian Hyde commented on CALCITE-1938: -- As for release number: I think we should keep continuity with the releases you have made already. So the next release would be 2.2.0. What do you think? > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (CALCITE-1938) First Apache release for Avatica Go
[ https://issues.apache.org/jira/browse/CALCITE-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16122813#comment-16122813 ] Francis Chuang commented on CALCITE-1938: - Thanks for opening this, Julian. I think we should use this JIRA to deal with the things we need to do to make the first release. Here are the things I feel must be completed before a first release can be tagged: * Switch CI to Apache Jenkins * Use self-hosted coverage reporting tool (maybe sonarqube's golang plugin) * Remove dependency on go-cleanhttp * Create release history page After release: * Update URL in the awesome-go list I think setting up CI should be something we make a move on first as that might require coordination with INFRA. Are you able to get the ball rolling for this one? > First Apache release for Avatica Go > --- > > Key: CALCITE-1938 > URL: https://issues.apache.org/jira/browse/CALCITE-1938 > Project: Calcite > Issue Type: Bug > Components: avatica-go >Reporter: Julian Hyde >Assignee: Francis Chuang > > Make a release for Avatica Go. > Release number is TBD. > This will be the first Apache release for Avacica Go, so expect more > diligence / issues than usual. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
