Copying here from PHOENIX-6348 and PHOENIX-6349 for greater exposure:

Let me know if the solution in PHOENIX-6349 is acceptable.
If I get the timely +1 for PHOENIX-6349, then I'll put up the
phoenix-thirdparty 1.1.0RC0 today,
so that we can have a phoenix-thirdparty release on Monday to Wendsday.
(Depending on whether we count the weekend into the compulsory 72 hour vote
window)

I think that PHOENIX-6349 is a worthwhile fix, as it lets us solve the
quoting/case sensitivity problems on the tools,
even if we decide not to fast track it to get into this release.

regards Istvan

On Fri, Jan 29, 2021 at 1:40 AM Jacob Isaac <jacobpisaa...@gmail.com> wrote:

> As I started testing the builds found a dependency issue -
> PHOENIX-6348
>
> This will need to be addressed as this affects core functionality related
> to running the IndexTool.
>
> Thanks
> Jacob
>
>
> On 2021/01/28 05:09:44, Xinyi Yan <yanxi...@apache.org> wrote:
> > Hello Everyone,
> >
> > This is a call for a vote on Apache Phoenix 4.16.0 RC0. This is the next
> > minor release of Phoenix 4, compatible with Apache HBase 1.3, 1.4, 1.5
> > and 1.6.
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache phoenix 4.16.0
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 4.16.0RC0
> > https://github.com/apache/phoenix/tree/4.16.0RC0
> >
> > The release files, including signatures, digests, as well as CHANGES.md
> > and RELEASENOTES.md included in this RC can be found at:
> > https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC0/
> >
> > For a complete list of changes, see:
> >
> https://dist.apache.org/repos/dist/dev/phoenix/phoenix-4.16.0RC0/CHANGES.md
> >
> > Artifacts are signed with my "CODE SIGNING KEY":
> > E4882DD3AB711587
> >
> > KEYS file available here:
> > https://dist.apache.org/repos/dist/dev/phoenix/KEYS
> >
> >
> > Thanks,
> > Xinyi
> >
>

Reply via email to