findepi commented on issue #13661:
URL: https://github.com/apache/datafusion/issues/13661#issuecomment-2520634686
> I would like to improve the testing / release process for DataFusion
releases to reduce the number of regressions found **after** release.
I agree with the goal, but i am concerned about the cost/overhead involved.
We don't have infinite bandwith at disposal.
Additionally, orchestrating testing across several downstream projects
creates new problems we didn't have before
- which downstream projects can stop the release train? what kind of
problems are able to stop the release train?
- this is especially important question for closed-source downstream
projects
- how long are we willing to wait for external teams to report back?
Downstream project maintainers will obviously be willing and motivated to help,
but their availability cannot be assumed
So what if we focused instead on:
- improving testing within DF itself? if a downstream project is concerned
about stability of feature X, they can contribute to improve test coverage for
feature X (eg https://github.com/apache/datafusion/issues/13470)
- easy low-overhead (automated) releases. If we see a big problem /
regression after a major release, this can be patched on a maintenance branch.
A maintenance branch can release daily without human intervention.
--
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: github-unsubscr...@datafusion.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org
