pingtimeout commented on PR #3256: URL: https://github.com/apache/polaris/pull/3256#issuecomment-3785516639
@RussellSpitzer We should certainly have a dev ML discussion about this. As you mentioned, there have been many PR in which we agreed to merge as-is and keep iterating/improving in follow-ups. So if we want to change that community practice, we should discuss it with the community. @flyrain - It sounds like you want to ensure we're making the right technical decision here, and I agree with you that it is critical we commit to the project's success. I think it's important we reflect on how our process aligns with Apache values, especially considering we are discussing graduation. The Apache Way emphasizes that contributions should be evaluated on their technical merit and demonstrated value, and that the decision making process should be open, transparent, and collaborative. I want to propose a path forward that honors both the Apache Way and respects everyone's contributions: 1. #3256 moves forward based on its demonstrated merit - it's tested, approved by diverse reviewers, and solves documented problems 2. #3415 can be evaluated independently on its own merits once it has comparable testing and validation. Both approaches can coexist. 3. We open another PR to add a feature flag that allows users to use the storage operations code for purge. The feature flag defaults to the current implementation (== no behaviour change in Polaris). This approach demonstrates the kind of open, collaborative, merit-based decision making that will serve us well as we work toward graduation. And it also enables the community to move forward. Am I missing anything that would make this path forward unreasonable? I would like to commit this by lazy consensus if no-one objects within the next two days. Let's use this PR reviews (Approval/Request for changes) to collect responses. cc @RusselSpitzer @dimas-b @adam-christian-software. -- 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]
