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

WIP: release process ascii diagram #5662

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

wesleytodd
Copy link
Member

I had started drafting this a bit back to try and clear up the 5.0 vs 5.x branch thing. I just added a little bit, but I don't think it is right to merge yet but also I didn't want it to get lost on my machine.

I think the main confusion with the 5.0 branch is that it exists instead of using individual release branches for the inital beta releases. I know the goal was to keep the prerelease verison commits out of the history and also not have individual branches littering around for the betas, but actually that might have made it easier now.

Anyway, I am going to see if I can get this PR into a shape where it is both a recommendation for a way (which @UlisesGascon also did in #5513) which is more simple. I will keep it in draft for now so it is clear this is not something to merge, but I am going to try and focus on the real work to get this stuff landed first. These branches are a distraction which we need to fix, but I think we can do it after we publish (as much as I know it has been a confusion for folks). Happy to help with anything in the mean time, but I just have limited time and don't want to try and make it perfect before we make it good.

@wesleytodd wesleytodd marked this pull request as draft May 13, 2024 21:22
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.

1 participant