True. But you will run into grief from the Apache release police if you do. I would strongly recommend following the recommendation. :)
> On Aug 28, 2018, at 4:23 PM, Michael Mior <[email protected]> wrote: > > Looks like a great plan. Thanks Francis :) > > Also, while I think we should drop the .md5 (and I don't see a good reason > not to), SHOULD NOT indicates that it's a recommendation, not a requirement. > > -- > Michael Mior > [email protected] > > > > Le mar. 28 août 2018 à 19:13, Julian Hyde <[email protected]> a écrit : > >> Thanks for driving this, Francis. >> >> Apache release policy and Calcite release practice have both changed >> recently: >> * Calcite no longer releases a .zip, only a .tar.gz; and we no longer >> release an .md5[1]. If you want to drop the .zip feel free; if not, that’s >> fine also. >> * Apache policy now says you SHOULD NOT release an .md5[2]; you must drop >> that from the release. >> >> Julian >> >> [1] >> https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.17.0-rc0/ >> <https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-1.17.0-rc0/ >>> >> >> [2] https://www.apache.org/dev/release-distribution.html#sigs-and-sums < >> https://www.apache.org/dev/release-distribution.html#sigs-and-sums> >> >> >>> 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 >>> >> >>
