Skip to content

[DISCUSS] More extensive pre-release testing #13661

Open
@alamb

Description

@alamb

Is your feature request related to a problem or challenge?

Up to now, when we have made DataFusion releases, we have mostly focused on validated that DataFusion's own unit tests have passed, (see dev/release/README.md) but haven't tested the upgrade with other downstream projects (like ballista, ray, InfluxDB IOx, etc) until after we have release the code

This results sometimes in downstream users finding issues after release. Some recent examples

Describe the solution you'd like

I would like to improve the testing / release process for DataFusion releases to reduce the number of regressions found after release.

This would likely take the form of updating the dev/release/README.md

Describe alternatives you've considered

One idea mentioned by @Omega359 and @andygrove on #13525 (comment)

Upgrading our own subprojects (Ballista, Comet, DF Python, DF Ray) as part of the DataFusion release process makes a lot of sense to validate that the upgrade guide is complete.

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions