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

Allow releasing 2.0.x branch #8732

Merged
merged 1 commit into from
Apr 11, 2024
Merged

Allow releasing 2.0.x branch #8732

merged 1 commit into from
Apr 11, 2024

Conversation

ghostdogpr
Copy link
Member

@ghostdogpr ghostdogpr commented Apr 9, 2024

I'd like to do a 2.0.x release with the performance improvements that have been pushed to that branch. I think that change is all we need to do that.

Independent question: what's the plan for 2.1? Are there more things to be included? Are the runtime changes complete/stable?

@jdegoes
Copy link
Member

jdegoes commented Apr 11, 2024

@ghostdogpr Mostly it just needs to be merged with master and we need to do one RC for 2.1. There's nothing else that needs to be in there, even though there is some followup work I will do in May.

@jdegoes jdegoes merged commit 0f88315 into zio:series/2.0.x Apr 11, 2024
20 checks passed
@ghostdogpr
Copy link
Member Author

Ah your 2.1 changes are already in the "main" branch (series/2.x), which is why I backported some improvements to series/2.0.x so we could release them.

@kyri-petrou and I are currently looking at the ForkJoin improvements, so I'll wait a bit to see if we find anything and then do a 2.1.0-RC2 (there was a RC1 in December).

@ghostdogpr ghostdogpr deleted the ci branch April 13, 2024 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants