Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

DataFusion 38.0.0 Release #10217

Closed
andygrove opened this issue Apr 24, 2024 · 13 comments
Closed

DataFusion 38.0.0 Release #10217

andygrove opened this issue Apr 24, 2024 · 13 comments
Assignees
Labels
enhancement New feature or request

Comments

@andygrove
Copy link
Member

andygrove commented Apr 24, 2024

Is your feature request related to a problem or challenge?

I plan on starting to prepare for the DataFusion 38 release on Monday, April 29th. Let's use this issue to track which issues/PRs need to be included.

This will be the first release as a top-level ASF project and there will likely be some additional work required.

Describe the solution you'd like

Issues/PRs to include:

Describe alternatives you've considered

No response

Additional context

37 release ticket: #9682

@andygrove andygrove added the enhancement New feature or request label Apr 24, 2024
@l1t1
Copy link

l1t1 commented Apr 26, 2024

please release the Python version too.

@andygrove
Copy link
Member Author

please release the Python version too.

We will need someone to make the necessary changes to the DataFusion Python subproject first, so that it compiles against the new version of DataFusion.

Is this something that you would be interested in helping with?

@andygrove andygrove self-assigned this Apr 26, 2024
@alamb alamb changed the title DataFusion 38 Release DataFusion 38.0.0 Release Apr 27, 2024
@alamb
Copy link
Contributor

alamb commented Apr 27, 2024

I added a few more items to the waiting list:

#10254
#10181
#10095

@alamb
Copy link
Contributor

alamb commented Apr 30, 2024

Added #9785 per #9785 (comment)

@andygrove
Copy link
Member Author

Hi @alamb. I assume we still want to wait on #10181 for creating the release?

@alamb
Copy link
Contributor

alamb commented Apr 30, 2024

Hi @alamb. I assume we still want to wait on #10181 for creating the release?

I think that would be good -- are you about ready to make a release candidate? If so I will work on #10181 tomorrow

@andygrove
Copy link
Member Author

Hi @alamb. I assume we still want to wait on #10181 for creating the release?

I think that would be good -- are you about ready to make a release candidate? If so I will work on #10181 tomorrow

I am ready any time.

@alamb
Copy link
Contributor

alamb commented May 1, 2024

Here is a PR witha proposed API #10330 that would close #10181

@alamb
Copy link
Contributor

alamb commented May 3, 2024

I also think #10320 should be included in 38.0.0 (as it would be a regression if we released main as is). There is a PR up to fix it here #10321

@andygrove
Copy link
Member Author

I will start the process of creating the first release candidate today.

@alamb
Copy link
Contributor

alamb commented May 7, 2024

@andygrove
Copy link
Member Author

Release has been completed

@alamb
Copy link
Contributor

alamb commented May 15, 2024

Filed #10517 for next one

@alamb alamb mentioned this issue May 15, 2024
4 tasks
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants