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 currently open and slated for 1.10[1], but we
won’t hold the release for them unless someone commits to fixing them by
linking them to 1612.)
Julian
[1]
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CALCITE%20AND%20fixVersion%20%3D%20avatica-1.10.0%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC<https://issues.apache.org/jira/issues/?jql=project%20=%20CALCITE%20AND%20fixVersion%20=%20avatica-1.10.0%20AND%20resolution%20=%20Unresolved%20ORDER%20BY%20due%20ASC,%20priority%20DESC,%20created%20ASC>
On May 11, 2017, at 7:39 AM, Josh Elser<[email protected]> wrote:
+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
prior.
On May 10, 2017 12:58, "Julian Hyde"<[email protected]> wrote:
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’ve had chance to fix bugs Z1 and Z2)?
Can someone volunteer to be release manager?
See the tracking JIRA case, https://issues.apache.org/
jira/browse/CALCITE-1612.
Julian
