Over 40 commits and 7 months since the last Avatica release. Is it about time
we had another? This will be the first release from the new repo, and with the
new source code structure.
Does anyone have any time constraints (must be done before X; or must be done
after Y; or please wait until I’v
+1 to a release in the May timeframe. I'd be happy to volunteer to RM
(since I expect some rough edges on the coattails of the git repo
separation).
May will also be busy for me, so I am happy to defer to someone else :). I
just wanted to warn that this release probably won't be as smooth as those
Thanks for volunteering. Can we shoot for a first RC by Fri 26th (2 weeks from
today)? If your schedule is too busy, let me know, and I’ll take the reins.
I have 2 blockers, as described in 1612. If anyone else has blockers, please
link them to 1612. (18 issues are currently open and slated for
Will do!
Julian Hyde wrote:
Thanks for volunteering. Can we shoot for a first RC by Fri 26th (2 weeks from
today)? If your schedule is too busy, let me know, and I’ll take the reins.
I have 2 blockers, as described in 1612. If anyone else has blockers, please
link them to 1612. (18 issues are
I'm working on an RC for Avatica now. I'm updating
https://issues.apache.org/jira/browse/CALCITE-1612 with progress, and
you may notice a few pushes to calcite/avatica branch-avatica-1.0.
Please ignore them.
On Fri, May 12, 2017 at 9:51 AM, Julian Hyde wrote:
> Thanks for volunteering. Can we sho
Thanks, Julian. The past few weeks have been atrocious for me at work.
I'll try to find evening time to look at the RC.
On 5/23/17 3:55 PM, Julian Hyde wrote:
I'm working on an RC for Avatica now. I'm updating
https://issues.apache.org/jira/browse/CALCITE-1612 with progress, and
you may notice
