alamb commented on issue #20088: URL: https://github.com/apache/datafusion/issues/20088#issuecomment-3834739840
I agree -- having this labeling would help a lot -- thanks @Jefffrey and @2010YOUY01 for the suggestion Maybe once we have it working reasonably we could even automate some of the workflows (aka merge after 24 hours, for example) I personally recommend starting with the smallest number of labels possible and then expand it if we find something that works well. Making a beautiful process that no one actually follows will just make the situation worse I think. Maybe something like this: * ready for committer - Needs a maintainer to review * pending author action - feedback provided, waiting on review * ready to merge - can be merged after 24 hour window The "needs discussion" is a tricky one -- is the point of marking a PR like this to try and get it more attention? I sort of worry labeling something "needs discussion" will end up making PRs impossible to merge as it won't be clear when we can restore them. > blocked: e.g. waiting for an arrow-rs update before it can proceed Note there is already a 'waiting on upstream' label that could be used for this purpose -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
