timsaucer opened a new issue, #21034: URL: https://github.com/apache/datafusion/issues/21034
This topic came up in the recent DataFusion community meeting. There is interest in having a retrospective of our current release practices. ## Background DataFusion major version 52 ended up with 4 releases and another underway: - https://github.com/apache/datafusion/issues/20855 - https://github.com/apache/datafusion/issues/20681 - https://github.com/apache/datafusion/issues/20287 - https://github.com/apache/datafusion/issues/19784 - https://github.com/apache/datafusion/issues/18566 At the same time we are trying to release [53.0.0](https://github.com/apache/datafusion/issues/19692). Trying to release patches on past versions while simultaneously releasing a new major version may split maintainer time and focus in undesirable ways. ## Additional references Discussion about the frequency of releasing: https://github.com/apache/datafusion/issues/16622 We are currently updating the release documentation: https://github.com/apache/datafusion/pull/21001 ## Request This issue is to collect feedback from all community members about the recent release process. The discussion above is where the topic of frequency should happen. There is a plan to have an in-person retrospective at the next community meeting, March 25. @mbutrovich has volunteered to try capturing notes from that meeting. For people who want to share thoughts asynchronously or cannot attend the community meeting, please give us your feedback about the recent release process. - What went well? - What could be improved? - What did we learn? - What should we commit to changing? -- 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]
