github: refactor: Introduce two-branch release cycle master-devel#632
Merged
Conversation
Adda0
force-pushed
the
releases-on-master
branch
4 times, most recently
from
42817f7 to
6ddb07d
Compare
Adda0
force-pushed
the
releases-on-master
branch
3 times, most recently
from
7712b3e to
f1a1d24
Compare
Adda0
force-pushed
the
releases-on-master
branch
3 times, most recently
from
c5db7a6 to
7f1dc89
Compare
This file contains hidden or 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
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.
This PR introduces a two-branch release cycle: normal releases on
masterand development releases ondevel, with final merging intomasterwhen the changes are ready. This allows gradual preparation for larger changes to the library, as well as continuous development without worrying about breaking userland.