alamb opened a new issue, #26865: URL: https://github.com/apache/datafusion/issues/26865
Recently there has been an explosion of new code going into DataFusion, as well as an explosion of new bug reports. Obviously these are both driven by new AI tools and we are all struggling to figure out how to adjust to the new software engineering realty DataFusion is also getting close to the 56 release - https://github.com/apache/datafusion/issues/24461 We also have a number of outstanding wrong results bugs: - https://github.com/apache/datafusion/issues/26672 Thus I would like to **discuss slowing down feature merging** for a while ( a few weeks?) while we sort out the bugs and harden the features / testing / docs we do have. I think we already risk this project running out of control / become unmaintainable (at least I would not be interesting in maintaining it) if we keep accepting new features at such a clip and accumulating maintenance surface and technical debt I would suggest something like: 1. maintainers focus on bug fixes, dev tooling improvements, simplifications, etc for the next few weeks 2. Prepare new feature PRs / test them / review them of course, but don't merge them until after 56 is out 3. Be even more aggressive about filtering out PRs that are risky or from non maintainers / existing community members -- 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]
