Skip to content

Release DataFusion 50.2.0 (minor) #17849

Closed

Description

@AdamGS

Is your feature request related to a problem or challenge?

There are some things that we may way to backport into the 50.0.0 line, and this ticket tracks doing so.

Steps

  • Update version and changelog
  • Test with DataFusion Python
  • Test with DataFusion Comet
  • Test with delta.rs:
  • Test Vortex
  • Test with iceberg-rust:
  • Test with LakeSail:
  • Test with parquet viewer
  • Test with datafusion-materialized-views
  • Voting Thread
  • Publish to crates.io
  • Create ticket for next release:

Potential Content:

Minor Features

Bug Fixes

Backport PR list:

Activity

  1. alamb commented on Sep 30, 2025

    @alamb
    Contributor

    I am happy to run this release process, unless @xudong963 or another PMC member wants to

  2. AdamGS commented on Sep 30, 2025

    @AdamGS
    ContributorAuthor

    Happy to help with anything I can do, I can start backporting changes once 50.1.0 is out.

  3. xudong963 commented on Oct 1, 2025

    @xudong963
    Member

    I can run this release process. I plan to leave the issue for 2 days to see if anyone else wants other PRs included.

  4. self-assigned this
    on Oct 1, 2025
  5. alamb commented on Oct 2, 2025

    @alamb
    Contributor

    It looks like there are a few PRs to backport but then we'll be ready to go

  6. AdamGS commented on Oct 2, 2025

    @AdamGS
    ContributorAuthor

    I have the second PR in the decimal open in my fork, once the first one merges I can open a PR targeting the branch (unless there's some github UI magic I'm missing, couldn't figure out another way to do that).

    edit: Added the docs fix backport PR to the top here.

  7. AdamGS commented on Oct 2, 2025

    @AdamGS
    ContributorAuthor

    Seems like some typos sneaked into main, whats the policy here? I can fix them but seems like if they made it in its fine to keep them there for now, as I do see that upstream someone already fixed them.

  8. alamb commented on Oct 2, 2025

    @alamb
    Contributor

    Seems like some typos sneaked into main, whats the policy here? I can fix them but seems like if they made it in its fine to keep them there for now, as I do see that upstream someone already fixed them.

    I think we should fix them in the branch so we can get a clean CI run. Maybe as a second PR 🤔

  9. AdamGS commented on Oct 2, 2025

    @AdamGS
    ContributorAuthor

    I'll open a PR later today

  10. AdamGS commented on Oct 3, 2025

    @AdamGS
    ContributorAuthor

    I've put up the last two PRs, there's a stacked diff thing here I'm not sure how to do with github's UI, but it should be easy enough to resolve.

  11. xudong963 commented on Oct 8, 2025

    @xudong963
    Member

    It seems all PRs are patched. I plan to release it at night.

  12. alamb commented on Oct 8, 2025

    @alamb
    Contributor

    Thank you @xudong963 !

  13. xudong963 commented on Oct 9, 2025

    @xudong963
    Member

    FYI, I just started the voting process

  14. xudong963 commented on Oct 13, 2025

    @xudong963
    Member

    Done

  15. alamb commented on Oct 14, 2025

    @alamb
    Contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions