Yes that sounds good, I also think we should wait for this to get merged.
I'll create another RC after this gets fixed.

Thanks

On Mon, May 12, 2025 at 3:04 AM Istvan Toth <st...@cloudera.com.invalid>
wrote:

>    1. I have noticed PHOENIX-7591
>    <https://issues.apache.org/jira/browse/PHOENIX-7591> . This test has
>    been flakey for some time, and based on Tanuj's comments, this looks
> like
>    a regression introduced after 5.2.2.
>
>    This sounds to me like a serious enough problem to block 5.2.2.
>
>    What do you think ? Should we wait until it is fixed ?
>
>    Istvan
>
>
> On Thu, May 8, 2025 at 1:31 AM Lokesh Khurana <loki...@apache.org> wrote:
>
> > Please vote on this Apache Phoenix release candidate, Phoenix-5.2.2RC3
> >
> > The VOTE will remain open for at least 72 hours.
> >
> > [ ] +1 Release this package as Apache Phoenix 5.2.2
> > [ ] -1 Do not release this package because ...
> >
> > The tag to be voted on is 5.2.2RC3:
> > https://github.com/apache/phoenix/tree/5.2.2RC3
> >
> > 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-5.2.2RC3/
> >
> > Maven artifacts are available in a staging repository at:
> >
> >
> https://repository.apache.org/content/repositories/orgapachephoenix-1270/
> >
> > Artifacts were signed with the A2CD967B key which can be found in:
> >
> > https://dist.apache.org/repos/dist/release/phoenix/KEYS
> >
> > To learn more about Apache Phoenix, please see
> >
> > https://phoenix.apache.org/
> >
> > Thanks,
> > Your Phoenix Release Manager
> >
>
>
> --
> *István Tóth* | Sr. Staff Software Engineer
> *Email*: st...@cloudera.com
> cloudera.com <https://www.cloudera.com>
> [image: Cloudera] <https://www.cloudera.com/>
> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
> Cloudera on Facebook] <https://www.facebook.com/cloudera> [image: Cloudera
> on LinkedIn] <https://www.linkedin.com/company/cloudera>
> ------------------------------
> ------------------------------
>

Reply via email to