Hi!

I have created https://issues.apache.org/jira/browse/PHOENIX-6700 to track
the packaging and HBase support changes for 5.2.
This includes patches for the topics recently discussed here on the list.

Please check the included tickets, and comment/review.

Istvan

On Thu, Apr 14, 2022 at 5:27 AM Istvan Toth <[email protected]> wrote:

> Hi!
>
> Browsing the list, your PHOENIX-6671
> <https://issues.apache.org/jira/browse/PHOENIX-6671> looks like something
> that should be resolved, as requiring the very latest HBase doesn't feel
> right.
>
> Also, I'd like to include phoenix-thirdparty 2.0, and after that do an
> Omid release, to get the pending fixes and improved build/dependency stuff
> included in 5.2.
>
> Thirdparty is already on vote, once that's done, the Omid stuff shouldn't
> take more than 2-3 weeks to get released and adopted in Phoenix.
>
> The only other things that come to my mind is a CVE sweep and some JIRA
> bookkeeping to make sure our changelog reflects the release.
>
> Istvan
>
> On Wed, Apr 13, 2022 at 11:13 PM Geoffrey Jacoby <[email protected]>
> wrote:
>
>> It's been about 10 months since our last patch release (5.1.2), and 14
>> months since our last minor release (4.16 and 5.1.0). In the interim we've
>> had some significant JIRAs come in, which would be good to get out to the
>> community. Some of these patches, such as online schema transforms, change
>> system metadata, which requires at least a minor release.
>>
>> So, what needs to be completed before we can cut a release? I currently
>> see
>> 55 non-resolved JIRAs with a Fix Version of 5.2.0.[1]
>>
>> I volunteer to RM a 5.2 release, unless someone else would like to do it.
>>
>> Thanks,
>>
>> Geoffrey Jacoby
>>
>> [1]
>>
>> https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20%22Patch%20Available%22)%20AND%20fixVersion%20%3D%205.2.0
>>
>
>
> --
> *István Tóth* | Staff Software Engineer
> [email protected] <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>
> <https://www.cloudera.com/>
> ------------------------------
>

Reply via email to