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

Update v5.0 with lastest v4.x releases #5439

Closed
wants to merge 1 commit into from

Conversation

UlisesGascon
Copy link
Member

No description provided.

@dougwilson
Copy link
Contributor

dougwilson commented Feb 4, 2024

Typically the merge will also update the needed deps that also have differring majors between 4 and 5 so the fixes and changes listed as done in 4 will actually land in 5.

If not, then just probably want to update the history file to clarify that it doesn't include x or y change from the 4 release mentioned.

@UlisesGascon
Copy link
Member Author

I think that I will change my approach on this update as the git historial is not as a clear as previous 5.x releases. I am thinking to go with cherry picking from the master branch but not sure also if this is the best approach. What do you recommend me to do @dougwilson ? How to do manage this sync processes? I will take this opportunity also to document it :)

@dougwilson
Copy link
Contributor

We can discuss once I get back next week :) I pretty much have this particular merge done too as I wqs working on it a couple weeks ago.

@UlisesGascon
Copy link
Member Author

We can discuss once I get back next week :) I pretty much have this particular merge done too as I wqs working on it a couple weeks ago.

Yep! Sounds great

@UlisesGascon
Copy link
Member Author

This was solved by @wesleytodd when releasing v5.x last time, so I close the PR :)

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.

2 participants