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

merge Release/3.1.0.0.0 to develop #5545

Closed
wants to merge 3 commits into from
Closed

merge Release/3.1.0.0.0 to develop #5545

wants to merge 3 commits into from

Conversation

wileyj
Copy link
Contributor

@wileyj wileyj commented Dec 8, 2024

changelog and #5538

@wileyj wileyj requested review from a team as code owners December 8, 2024 17:22
@obycode
Copy link
Contributor

obycode commented Dec 8, 2024

Is it better to just merge release -> master, then master -> develop?

@wileyj
Copy link
Contributor Author

wileyj commented Dec 9, 2024

Is it better to just merge release -> master, then master -> develop?

i don't feel strongly one way or the other. i think if we did what you propose though, it may reduce potential for conflicts (basically only resolve once).

i can update release docs to reflect this and start using that method for future releases unless anyone else feels strongly for a different approach.

@obycode the downside to this approach (which may be solved by some automation) is that there will be a delay from merging a release branch into develop, since it would first require a merge to master.

@wileyj
Copy link
Contributor Author

wileyj commented Dec 9, 2024

closing in favor of #5550

@wileyj wileyj closed this Dec 9, 2024
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.

3 participants