singhpk234 commented on PR #2877: URL: https://github.com/apache/polaris/pull/2877#issuecomment-3445622888
> But then we need to deal with angry users, we've seen this already: https://github.com/apache/polaris/issues/2671. https://github.com/apache/polaris/issues/2671 was a bug, which made user upgrade from 1.0.1 to 1.1.0 fail, for already bootstraped realms fail, we fixed it in 1.2, IMHO its a bit orthogonal to this discussion. > I think being open and honest about the state of Polaris features is key in building a trust relationship with the community. Agree with you on this ! but where are we being dishonest ? we are just saying hey this is something we have, try it out if you want to, if we put out a breaking change we should call it out in our release docs, reconsider that there is users using it and make change accordingly and this is true for any features we ship. If the rationale is there is going to be breaking change for sure regarding **_events_** and the community agrees to (which my understanding is what your and @dimas-b feedback is). I propose i remove the CloudWatch sink from the release notes and we mark CloudWatch sink as beta in the follow-up when we have concencus on thread @dimas-b started. We already have release artifacts published in maven https://mvnrepository.com/artifact/org.apache.polaris/polaris-core as of (10/23), It would be great to move forward with this PR. Please let me know your thoughts ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
