Towards Avatica-Go release ?.?

We have to make a release of Avatica Go soon (like, within the next month). As I’ve said previously, a tar-ball of the source (plus checksums/signatures and release notes) is sufficient. But we are an Apache project, and projects must make releases. Can someone please volunteer to be release ma

Re: Towards Avatica-Go release ?.?

I am wrapping up some things today and plan to test Avatica Go against the latest version of Avatica. I think we'll be able to make a release by the end of the week. I am happy to be the release manager for this one. The latest version of Avatica is 2.3.1 under Boostport/avatica, I think we s

Re: Towards Avatica-Go release ?.?

Thanks, Francis. The most important step is to come up with a release vote email with the same items as [1]: release notes, git commit, artifacts to be voted on in dist.apache.org/repos/dist/dev , md5 and sha256 hashes. (The staged maven repository does no

Re: Towards Avatica-Go release ?.?

Thanks Francis for taking this on! -- Michael Mior mm...@apache.org 2018-04-09 18:26 GMT-04:00 F21 : > I am wrapping up some things today and plan to test Avatica Go against the > latest version of Avatica. > > I think we'll be able to make a release by the end of the week. > > I am happy to be

Re: Towards Avatica-Go release ?.?

Hey Julian, The code is in a releasable state. A few questions: - Building a binary of a library in Go is not useful/meaningful. For the release, we just need to tar gz the git repo and sign it. Do you still need a script for this? Otherwise we can write the instructions somewhere in the site/

Re: Towards Avatica-Go release ?.?

Yes, the script isn’t very complicated. We probably need half a dozen lines of shell script to create the tar.gz file, sign it, and generate .sha256 checksums. I don’t mind where you put those lines of shell script, as long as the next RM can find them. The site looks good. It doesn’t have to b

Re: Towards Avatica-Go release ?.?

Thanks, Julian. I will add a release script to the repo and add the release notes to the site/ directory. I also had to make some breaking changes to the public interfaces with the updates, so we'll release it as 3.0.0. Francis On 16/04/2018 4:44 PM, Julian Hyde wrote: Yes, the script isn’t

Re: Towards Avatica-Go release ?.?

Julian, The release (3.0.0-rc0) is ready for voting. Do the artifacts need to be uploaded before sending out the release email? If so, can you please sign them? Instructions for making and signing release artifacts are here: https://github.com/apache/calcite-avatica-go/blob/master/site/go_dev

Re: Towards Avatica-Go release ?.?

Yes, they need to be uploaded to dist/dev. I will generate them and sign them (I can't sign them if I’m not sure they’re genuine!) and then upload them. I’ll let you know. Julian > On Apr 16, 2018, at 10:01 PM, Francis Chuang wrote: > > Julian, > > The release (3.0.0-rc0) is ready for votin

Re: Towards Avatica-Go release ?.?

I’m at a conference today and having problems using gpg remotely. I’ll sign and upload the files tonight. > On Apr 17, 2018, at 9:34 AM, Julian Hyde wrote: > > Yes, they need to be uploaded to dist/dev. I will generate them and sign them > (I can't sign them if I’m not sure they’re genuine!) a

Re: Towards Avatica-Go release ?.?

Thanks, Julian. I just noticed that the script `make-release-artifacts.sh` was not committed with the executable bit fixed. I have pushed a commit to fix that, but you'll need to make it executable to sign the release for 3.0.0-rc0. Francis On 18/04/2018 3:55 AM, Julian Hyde wrote: I’m at

Re: Towards Avatica-Go release ?.?

I noticed the missing execute bit too. Thanks for the fix, Francis. I added an 'apache-' prefix to the file names, and removed '-rc0' from the file names (but not the directory name). The files for review are here: https://dist.apache.org/repos/dist/dev/calcite/apache-calcite-avatica-go-3.0.0-rc0

Re: Towards Avatica-Go release ?.?

Thanks for signing and uploading the artifacts! I will get the vote started ASAP. Francis On 18/04/2018 6:04 PM, Julian Hyde wrote: I noticed the missing execute bit too. Thanks for the fix, Francis. I added an 'apache-' prefix to the file names, and removed '-rc0' from the file names (but no

Re: Towards Avatica-Go release ?.?

Julian, Can you please review PR #22[1] for calcite-avatica-go? I also have some documentation fixes in a PR #20[2], and since we are going to cancel the vote for rc0 and roll rc1, I think it would be a good idea to merge that PR in too. Francis [1] https://github.com/apache/calcite-avatica-

Re: Towards Avatica-Go release ?.?

I've reviewed it. Fine to include doc. As a policy I tend not to include anything non-trivial in later release candidates, to avoid putting bumps in the road, but documentation is fine. On Fri, Apr 20, 2018 at 8:11 PM, Francis Chuang wrote: > Julian, > > Can you please review PR #22[1] for calci

Re: Towards Avatica-Go release ?.?

Hey Julian, Thanks for the review! The script has also been updated to allow the releaser to select a tag during build (defaults to the latest tag if no tag is entered). I've pushed the 3.0.0-rc1 tag to the repository. Can you build the artifacts and sign them please? Instructions for buildi