Skip to content

Release DataFusion 46.0.1 Patch or 46.1.0 minor release (March 2025) #15151

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Closed
3 tasks done
alamb opened this issue Mar 11, 2025 · 16 comments
Closed
3 tasks done

Release DataFusion 46.0.1 Patch or 46.1.0 minor release (March 2025) #15151

alamb opened this issue Mar 11, 2025 · 16 comments
Labels
enhancement New feature or request

Comments

@alamb
Copy link
Contributor

alamb commented Mar 11, 2025

Is your feature request related to a problem or challenge?

We recently released DataFusion 46:

We have a plan to release DataFusion 47 in a month:

However, since the release of 46 there have been a few reported issues that I think warrant potentially releasing a fix release for

Regressions

Describe the solution you'd like

I would like to release DataFusion 46.0.1 with fixes for the above issues (and anything else we encounter)

Describe alternatives you've considered

No response

Additional context

No response

@alamb alamb added the enhancement New feature or request label Mar 11, 2025
@alamb
Copy link
Contributor Author

alamb commented Mar 11, 2025

FYI @xudong963

@Omega359
Copy link
Contributor

Seems reasonable to me

@alamb alamb changed the title [DISCUSS] Release DataFusion 46.0.1 Patcheset (March 2025) [DISCUSS] Release DataFusion 46.0.1 Patch or 46.1.0 minor release (March 2025) Mar 11, 2025
@xudong963
Copy link
Member

+1

@xudong963
Copy link
Member

After all related issues are solved, should we go through the process of releasing again? Such as voting in dev list.

@alamb
Copy link
Contributor Author

alamb commented Mar 12, 2025

After all related issues are solved, should we go through the process of releasing again? Such as voting in dev list.

I think we need to do a full on release

The process would be:

  1. Backport the fixes to branch-46 (looks like this one is still outstanding)
  2. Update version + changelog
  3. Make a new RC + vote

@xudong963
Copy link
Member

After all related issues are solved, should we go through the process of releasing again? Such as voting in dev list.

I think we need to do a full on release

The process would be:

  1. Backport the fixes to branch-46 (looks like this one is still outstanding)
  2. Update version + changelog
  3. Make a new RC + vote

Nice, I'll do it after all todos are done

@alamb
Copy link
Contributor Author

alamb commented Mar 13, 2025

Once we have that merged (or decide we don't need it) let's make an RC and start voting

@alamb
Copy link
Contributor Author

alamb commented Mar 14, 2025

@alamb
Copy link
Contributor Author

alamb commented Mar 14, 2025

I have made the backport PRs:

I'll try and get them merged today and then I think we can make release notes and prep an RC

@xudong963
Copy link
Member

I'll try and get them merged today and then I think we can make release notes and prep an RC

Hi @alamb , I'm going to bed, I'll start the release process tomorrow

@alamb
Copy link
Contributor Author

alamb commented Mar 14, 2025

THanks @xudong963 -- I merged the outstanding issues. I think it should be good to go now

@alamb
Copy link
Contributor Author

alamb commented Mar 16, 2025

@xudong963 I haven't seen a vote thread on the mailing list yet. Would you like me to make a release candidate to start the process?

@xudong963
Copy link
Member

@alamb Sure, sorry I I got the process order wrong(I thought I should start the voting after #15244), now I believe after #15243, we can start the process!

@alamb
Copy link
Contributor Author

alamb commented Mar 17, 2025

Thanks again @xudong963 !

@xudong963
Copy link
Member

xudong963 commented Mar 19, 2025

Just a reminder, we can do a final release today, it seems to require a PMC member to do the last steps. cc @alamb.

@alamb
Copy link
Contributor Author

alamb commented Mar 19, 2025

Thanks @xudong963 -- I did so and published to crates.io!

Mailing list thread: https://lists.apache.org/thread/nmgp1lzq6kv6gtjvcwvky2f3rdw2kl1d

And with that onwards !

@alamb alamb closed this as completed Mar 19, 2025
@alamb alamb changed the title [DISCUSS] Release DataFusion 46.0.1 Patch or 46.1.0 minor release (March 2025) Release DataFusion 46.0.1 Patch or 46.1.0 minor release (March 2025) Mar 28, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants