Skip to content

Release DataFusion 52.3.0 (minor/) Release (Mar 2026) #20681

Description

@hareshkh

Is your feature request related to a problem or challenge?

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
  • Ensure all fixes here also make their way to branch-53 - Release DataFusion 53.0.0 (Feb 2026 / Mar 2026) #19692 (comment)
  • Publish to crates.io

Potential Content:

Requested Bug Fixes. Issue / requester / Backport

Activity

  1. mbutrovich commented on Mar 4, 2026

    @mbutrovich
    Contributor

    Comet could really use this fix in DF 52. #20482 @rluvaton will this be a straightforward backport?

  2. mbutrovich commented on Mar 4, 2026

    @mbutrovich
    Contributor

    Comet could really use this fix in DF 52. #20482 @rluvaton will this be a straightforward backport?

  3. alamb commented on Mar 4, 2026

    @alamb
    Contributor

    Thank you @hareshkh for filing this -- this is awesome.

    I am happy to help do the PMC only part of this (aka make a release candidate / do the official vote / publish to crates.io)

    Selfishly we also found a new bug in our testing too so it is in my own self interest too :)

  4. alamb commented on Mar 4, 2026

    @alamb
    Contributor

    I would also like to include the fix for this into 52.3.0 if possible:

    Once it gets merged I will make a backport to branch-52 as well

  5. comphead commented on Mar 4, 2026

    @comphead
    Contributor

    with releases and patches ongoing, I'm also wondering how to ensure some patch was backported to 52 from main but also missing from 53 🤔

  6. hareshkh commented on Mar 4, 2026

    @hareshkh
    ContributorAuthor

    Thanks @mbutrovich @alamb - I have included your suggested issues/PRs in the issue description as well.

    @comphead - Thankyou for flagging! For now I can do a manual audit and ensure fixes that are on this issue are also backported to/part of branch-53 before closing this issue. Open to other ideas as well to better coordinate this!

    For now, I have added a task in the this ticket's description - Ensure all fixes here also make their way to branch-53

  7. comphead commented on Mar 4, 2026

    @comphead
    Contributor

    For now, I have added a task in the this ticket's description - Ensure all fixes here also make their way to branch-53

    Thank you @hareshkh

  8. timsaucer commented on Mar 4, 2026

    @timsaucer
    Member

    I can help shepherd this along because I have a PR I am about to put up that should get into 52 (and 53)

    #20705

  9. alamb commented on Mar 4, 2026

    @alamb
    Contributor

    I also found that my reproducer for #20696 hit another bug (since fixed on main)

  10. mbutrovich commented on Mar 5, 2026

    @mbutrovich
    Contributor

    Assuming our benchmarks this afternoon show a good result, I will open backport PRs for #20729 as soon as it merges into main.

  11. mbutrovich commented on Mar 5, 2026

    @mbutrovich
    Contributor
  12. alamb commented on Mar 6, 2026

    @alamb
    Contributor

    How is this release shaping up? Are we ready to make a PR to update the release notes and version?

  13. 8 remaining items

  14. timsaucer commented on Mar 8, 2026

    @timsaucer
    Member

    I will start building the RC as soon as CI finishes on #20790

  15. timsaucer commented on Mar 8, 2026

    @timsaucer
    Member
  16. alamb commented on Mar 9, 2026

    @alamb
    Contributor

    We already at the threshold for binding votes. Now we just need to let the time elapse

    @timsaucer I added you as owner to the datafusion crates on crates.io (you'll have to accept them in order to publish the release)

    Thank you again for helping run this

  17. 16pierre commented on Mar 9, 2026

    @16pierre

    👋 Are we still in time for a bugfix on this issue #20724 ?

  18. xanderbailey commented on Mar 9, 2026

    @xanderbailey
    Contributor

    👋 Are we still in time for a bugfix on this issue #20724 ?

    Not a maintainer so I may be incorrect but from previous experience, after voting has started I think the train may have left the station for this particular release.

  19. timsaucer commented on Mar 9, 2026

    @timsaucer
    Member

    👋 Are we still in time for a bugfix on this issue #20724 ?

    I see the issue but I don't see an associated PR with a correction. We do have the release vote already underway, and without a PR I don't think we'd want to hold up the other corrections. We also have 53.0 release coming up: #19692

  20. alamb commented on Mar 10, 2026

    @alamb
    Contributor

    I have been behind on reviews but I have seen several other PRs that fix bugs / regressions introduced in 52 (and we hit another one at InfluxData yesterday), specifically this one that is not in 52 yet

    I was planning to spend my time trying to make sure 53 has all the fixes, but realistically if there is demand and bandwidth to help we may need a 52.4.0 as well 🤔

  21. alamb commented on Mar 10, 2026

    @alamb
    Contributor

    I filed a ticket to track another potential 52 release

  22. timsaucer commented on Mar 12, 2026

    @timsaucer
    Member

    Crates are published. Thank you everyone for the work on this.

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

Metadata

Metadata

Assignees

No one assigned

    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