I use my PR #135 for testing stuff using the CI infrastructure. It
does not need to go into 1.18 (or any release).

On Tue, Feb 16, 2021 at 6:59 AM Josh Elser <els...@apache.org> wrote:
>
> No, I wouldn't wait around for #132. When I left this off, I was
> debugging some JVM internals to understand why stuff didn't work :)
>
> Thanks for asking!
>
> I'll try to find some time to help on the other PR's you mentioned.
>
> On 2/15/21 4:54 PM, Francis Chuang wrote:
> > Hey Everyone,
> >
> > I am planning to make rc0 available for voting in the next few days.
> >
> > I think #129 is pretty much ready for merging. Danny, can you please
> > take a look?
> > - https://github.com/apache/calcite-avatica/pull/129
> >
> > Julian and Josh, do you guys think you will be able to get your PRs into
> > this release?
> >
> > - https://github.com/apache/calcite-avatica/pull/135
> > - https://github.com/apache/calcite-avatica/pull/132
> >
> > Francis
> >
> > On 3/02/2021 12:50 pm, Francis Chuang wrote:
> >> Hey everyone,
> >>
> >> It's been around 7 months since the last Avatica release. There has
> >> been some push to get 1.18.0 out before the Calcite 1.27.0 release, so
> >> that the fixes in 1.18.0 can make it into the Calcite release.
> >>
> >> I saw a few open PRs on Github that could be potentially merged for
> >> this release:
> >> - https://github.com/apache/calcite-avatica/pull/135
> >> - https://github.com/apache/calcite-avatica/pull/132
> >> - https://github.com/apache/calcite-avatica/pull/129 <- this one is
> >> pretty much ready to merge except for the commit message
> >> - https://github.com/apache/calcite-avatica/pull/115 <- it would be
> >> nice if someone could carry this one, I think this one is almost there
> >>
> >> Are there any other PRs to merge or issues to look at?
> >>
> >> There hasn't been a whole lot of commits since the last release, so I
> >> think this release should be pretty straight forward. It would be much
> >> appreciated if the community can have a look at those PRs I have
> >> highlighted.
> >>
> >> Francis

Reply via email to