Use newer SC version on the develop branch #5566
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
|
Another proposed suffix name is |
|
At the dev meeting we opted for EDIT: I will updated the wiki docs once this is merged. |
|
Since 3.12.2 is coming shortly, I'll wait for the release so that we don't have to fix the conflict this time. |
dyfer
force-pushed
the
topic/update-version
branch
from
4a99771
to
95dfb36
Compare
dyfer
force-pushed
the
topic/update-version
branch
from
95dfb36
to
6e35450
Compare
|
ready for review! |
joshpar
approved these changes
Jan 11, 2022
|
I've updated the wiki: https://github.com/supercollider/supercollider/wiki/git-workflow-and-guidelines#versioning please let me know if anything needs to be changed. I'll submit a PR with the update to the python script soon. |
4 tasks
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.
Purpose and Motivation
As discussed in supercollider/rfcs#16, I'd like to propose that the builds from the
developbranch indicate the "next" SC version, along with the appropriate suffix, like-prereleaseor-preview. This change has been briefly discussed with @joshpar and @jrsurge during the dev meeting on 2021-09-05 and I'm open to further suggestions on this.One expected side effect of this is that any future merges from the
<release>/mainbranch intodevelopwould need to resolve the conflict inSCVersion.txt(only once per version change though). The version on the develop brach should still stay as the "next" version.Types of changes
To-do list