Track Bevy release on default branch #205
Merged
Conversation
This file contains 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
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Since Bevy adopted a train release schedule, it makes less sense to closely track Bevy's
mainbranch. This PR will make themasterbranch depend on Bevy 0.10. I already pushed abevy-mainbranch that tracks Bevy as we always did. I also adapted the GitHub Actions workflows to also work withbevy-main.The new PR policy will be that changes should be targeted preferably on the
masterbranch, whilebevy_mainis for fixing breaking changes and for using Bevy features not yet supported on release.TODO
Contributing.mdguide to help developers choose the right target branch. This will be done in a separate PR.bevy-mainintomaster, needed each time a new Bevy version releases.