I've just found another important one: PHOENIX-5215 <https://issues.apache.org/jira/browse/PHOENIX-5215> for the HTrace replacement.
On Mon, Apr 3, 2023 at 4:12 PM Istvan Toth <[email protected]> wrote: > Hi! > > We were planning to release 5.2 last summer, but those plans fell through. > > I think it's time to have another go. > > I consider the following issue a hard blocker: > PHOENIX-6898 <https://issues.apache.org/jira/browse/PHOENIX-6898> > > and I am aware of the following ongoing work which we probably want to > include: > PHOENIX-6910 <https://issues.apache.org/jira/browse/PHOENIX-6910> > PHOENIX-6888 <https://issues.apache.org/jira/browse/PHOENIX-6888> > PHOENIX-6916 <https://issues.apache.org/jira/browse/PHOENIX-6916> (I'm > working on this now) > > WDYT ? > Should we aim towards a release in Spring/Early Summer ? > Do you have any other issues that you want to classify as a blocker > (please set the priority) ? > Are you working on anything that you want to include in 5.2 ? > > My own mid-term priorities are further date handling improvements in > PHOENIX-6882 <https://issues.apache.org/jira/browse/PHOENIX-6882> and the > client/server code split in PHOENIX-6053 > <https://issues.apache.org/jira/browse/PHOENIX-6053>, but I'm fine with > those slipping to 5.3. > > Looking forward to hearing your thoughts. > > Istvan > > For reference, these are the open tickets with 5.1.x / 5.2.0 versions set > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20PHOENIX%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened%2C%20%22Patch%20Available%22)%20AND%20affectedVersion%20in%20(5.1.0%2C%205.1.1%2C%205.1.2%2C%205.1.3%2C%205.1.4%2C%205.2.0)%20ORDER%20BY%20summary%20ASC > > > >
