I will also be including the transition plan in the release notes and
the news item for the release. The JIRA case is CALCITE-2335.
I believe zip archives were removed, but I will check to confirm.
I will also check to confirm if we are still releasing a .md5 for
Avatica-Go. MD5 is easily crackable with modern computing power, so I
will remove it if we are still releasing it.
Francis
[1]https://issues.apache.org/jira/projects/CALCITE/issues/CALCITE-2335
On 29/08/2018 9:18 AM, Julian Hyde wrote:
Also, it’s helpful that you are publishing the transition plan up-front. Do you
plan to include it in the release notes, or perhaps reference a JIRA case?
Users of avatica-go may not be subscribed to this list, but they still need to
be aware of the transition plan.
On Aug 28, 2018, at 4:05 PM, Francis Chuang <[email protected]> wrote:
Hi all,
I'd like to start a vote for Avatica-Go 3.1.0 over the next few days.
Some key things I'd like to address in this release:
- Go 1.11 was released a few days ago and now includes support for dependency management
using "Go modules" (done).
Some history:
The Go community released a package manager called Dep[1] in the middle of
2017. Dep is designed to be very similar to npm, composer and cargo. Initially,
this was poised to be the official package manager for Go. At the beginning of
2018, Russ Cox (a member of the Go team) announced vgo (aka Go modules) which
is a different approach to package management for Go. While there was some push
back from the community working on Dep, Go modules is now officially in the Go
tool chain and will be the package management solution of choice for all Go
projects.
Transition plan for Avatica-Go:
Avatica-Go currently uses Dep and has the Gopkg.toml and Gopkg.lock files
committed. In terms of the Go team, the current (1.11) and last (1.10) versions
of Go are the actively maintained versions. Since Go 1.10 does not have support
for Go modules (but there was a patch release to support Go modules import
paths to work with libraries using Go modules), we need to keep Dep in place
for now. I have added support for Go modules (go.mod and go.sum files) to
support people using Go modules for package management. When Go 1.12 is
released in early 2019, I will remove support for Dep and all users will be
required to use Go modules. This will allow us to simplify the configuration
for continuous integration and the documentation for using and releasing
Avatica-Go.
- Update dependencies (done).
- Test against Avatica 1.12 and Phoenix 5.0.0 (in progress).
- Update documentation (in progress).
This release should be pretty routine and there should be no significant
changes. I will send another email to start a vote in the next few days. If you
have any comments or questions, please let me know.
Francis
[1] https://github.com/golang/dep/releases
