Skip to content

Release arrow-rs / parquet Minor version 60.2.0 (November 2026) #10526

Open

Description

@alamb

Let's keep the code flowing. Part of

Release Checklist:

Required items for release

Requested items for release

Activity

  1. changed the title [-]Release arrow-rs / parquet Minor version 60.2.0 (October 2026)[/-] [+]Release arrow-rs / parquet Minor version `60.2.0` (October 2026)[/+] on Aug 3, 2026
  2. mbutrovich commented on Oct 7, 2026

    @mbutrovich
    Contributor

    #11425 I would be interested in backporting this for Comet once it merges into main. I think it would be allowed under the API policy.

  3. Jefffrey commented on Oct 8, 2026

    @Jefffrey
    Contributor

    @mbutrovich are you commenting on the right issue here? did you mean to comment on #11352 for a backport 🤔

  4. mbutrovich commented on Oct 8, 2026

    @mbutrovich
    Contributor

    @mbutrovich are you commenting on the right issue here? did you mean to comment on #11352 for a backport 🤔

    I missed that we had a 59.x minor release cooking too, thanks!

  5. changed the title [-]Release arrow-rs / parquet Minor version `60.2.0` (October 2026)[/-] [+]Release arrow-rs / parquet Minor version `60.2.0` (November 2026)[/+] on Oct 23, 2026
  6. Jefffrey commented on Oct 24, 2026

    @Jefffrey
    Contributor

    could consider testing out Apache Trusted Releases (ATR) platform for this release 🤔

  7. self-assigned this
    on Oct 24, 2026
  8. comphead commented on Oct 27, 2026

    @comphead
    Contributor

    I would love to see #11552 in 60.2.0

  9. dejankrak-db commented on Nov 4, 2026

    @dejankrak-db
    Contributor

    Could #11877 (Parquet FILE logical type as the arrow.parquet.file extension type, behind file_experimental) go out in 60.2.0? It is additive and feature-gated, and delta-kernel-rs would use it to write file columns. Thanks!

  10. Jefffrey commented on Nov 5, 2026

    @Jefffrey
    Contributor

    15. Could #11877 (Parquet FILE logical type as the arrow.parquet.file extension type, behind file_experimental) go out in 60.2.0? It is additive and feature-gated, and delta-kernel-rs would use it to write file columns. Thanks!

    considering its merged to main already, itll be packaged as part of 60.2.0, barring any issues during release testing

  11. comphead commented on Nov 5, 2026

    @comphead
    Contributor

    I would love to see #11552 in 60.2.0

    I created #12094 and #12093

    Would be super helpful to land this in 60.2.0

  12. Jefffrey commented on Nov 11, 2026

    @Jefffrey
    Contributor

    Planning to begin this release, hopefully cut an RC by this weekend or the start of next week

    edit: I haven't had time to read through the ATR docs properly so I'll probably defer that for v61

  13. Jefffrey commented on Nov 12, 2026

    @Jefffrey
    Contributor

    ill cut an RC for this next week, perhaps tuesday or wednesday, to give some time in case there are desired PRs for this release

  14. etseidl commented on Nov 13, 2026

    @etseidl
    Contributor

    I'm hoping to get #11475 across the finish line for this release

  15. Jefffrey commented on Nov 13, 2026

    @Jefffrey
    Contributor

    added #11511 and #12154 as requested on slack

    (edit: fyi i likely wont be able to review PRs until tuesday)

  16. alamb commented on Nov 13, 2026

    @alamb
    ContributorAuthor

    I will make a push to rty and review these things later this afternoon

  17. Rich-T-kid commented on Nov 13, 2026

    @Rich-T-kid
    Contributor

    maybe this as well if i can get good numbers on the datafusion benchmarks on early iterations #12195

  18. alamb commented on Nov 13, 2026

    @alamb
    ContributorAuthor

    It is always tempting to cram more stuff into a release, but we always have the next one. Speaking of which I am thinking maybe we can plan to do a 60.3.0 rather than jump right to 61 as there aren't that many breaking changes queued up yet and releasing in 60 means we'll get it downstream faster.

    I'll file a ticket to propose that

  19. alamb commented on Nov 13, 2026

    @alamb
    ContributorAuthor

    Here is my proposal for a 60.3 release (and delay 61)

  20. Rich-T-kid commented on Nov 14, 2026

    @Rich-T-kid
    Contributor

    It is always tempting to cram more stuff into a release, but we always have the next one. Speaking of which I am thinking maybe we can plan to do a 60.3.0 rather than jump right to 61 as there aren't that many breaking changes queued up yet and releasing in 60 means we'll get it downstream faster.

    sounds good to me

  21. Jefffrey commented on Nov 17, 2026

    @Jefffrey
    Contributor

    I will cut an RC for this tomorrow. Any PRs that don't make it, we can include in 60.3.0 release.

  22. Jefffrey commented on Nov 18, 2026

    @Jefffrey
    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