Draft
Conversation
wmTJc9IK0Q
force-pushed
the
duckdb-1.5
branch
from
c8e2db1 to
53b77af
Compare
Collaborator
Yes, it'll also help with spreading the post-release workload as we can already implement new features on these preview versions. We would just have to find a maintainable update-interval of that preview branch. And we should wait until the work here makes the number of tags more manageable. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Keeping this branch open for now as I work on duckdb/duckdb-go#71 and the associated C API PR: duckdb/duckdb#20210
In the future, it'd be nice to keep a preview branch that tracks DuckDB main with new changes.