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.

Sign up for GitHub

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

Jump to bottom

Implement new release process #622

Closed
andygrove opened this issue Jan 22, 2023 · 0 comments · Fixed by #623
Closed

Implement new release process #622

andygrove opened this issue Jan 22, 2023 · 0 comments · Fixed by #623
Labels
enhancement New feature or request

Comments

@andygrove
Copy link
Member

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
Development of Ballista has been lagging behind DataFusion because we have to wait four weeks to get the next DataFusion release before we can update this repo.

I would like to change our release process and branch policy so that we can keep the main branch up-to-date with the latest DataFusion using GitHub dependencies and then create release branches when we are ready to create a new release.

Describe the solution you'd like
I will create a PR with the proposed solution.

Describe alternatives you've considered

Additional context
@andygrove andygrove added the enhancement New feature or request label Jan 22, 2023
@andygrove andygrove mentioned this issue Jan 22, 2023
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Implement new release process andygrove/datafusion-ballista
1 participant
@andygrove