Hi, I wanted to bring up wrong results in Phoenix and some JIRAs around them that I think we should fix as the wrong result lessens the end user's trust in Phoenix. Releasing a new version without addressing these in a minor release hurts our visibility in that these critical issues are not addressed.
Jira's that I'm involved with for example: I've already given a patch several months ago for 5833 and there is a chance it may fix 5484. https://issues.apache.org/jira/browse/PHOENIX-5833 https://issues.apache.org/jira/browse/PHOENIX-5484 In addition, inspecting apache JIRA i see several other wrong result JIRAs from the community. Some of these certainly are probably old issues or incorrect understanding but some of these are opened by our own dev community and are likely real problems. https://issues.apache.org/jira/browse/PHOENIX-6217 https://issues.apache.org/jira/browse/PHOENIX-5571 https://issues.apache.org/jira/browse/PHOENIX-4642 https://issues.apache.org/jira/browse/PHOENIX-4540 https://issues.apache.org/jira/browse/PHOENIX-4504 https://issues.apache.org/jira/browse/PHOENIX-4419 https://issues.apache.org/jira/browse/PHOENIX-4116 What is our stance on this type of issue? Are we going to say these were issues prior to 4.15 and not address them? Should we have requirements for our releases to fix wrong results? Daniel Wong On Mon, Nov 30, 2020 at 7:30 PM Xinyi Yan <yanxi...@apache.org> wrote: > Hi all, > > It's time to discuss the Phoenix 4.16 release. After many people's > contributions on the bug fixes, new features, and other works in the past > few months, we are kind of close to the point to have a RC (still need to > fix test flappers). Please let me know if you think any JIRA must be part > of the Phoenix 4.16 release other than major blocker PHOENIX-5712. > > If no surprise comes up, I will not wait for any new major features and > focus on the RC as soon as possible. > > Sincerely, > Xinyi > -- Daniel Wong Salesforce Mobile: 628.217.1808
