Branches #43
VelocityDesign
started this conversation in
Proposals
Replies: 2 comments 3 replies
-
dev and beta channels of software updates are both distributed as builds, and packaged into releases. From their, the source code of the release can be downloaded. Also an option, going into the branches interface and clicking the tags tab will allow you to view the source code of the release. Your method does not seem necessary. |
Beta Was this translation helpful? Give feedback.
3 replies
-
This is being tested with v3.10s development cycle. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Idea: Add separate branches for commits to go through
This would create a stable workflow. Commits would start in the "dev" branch, be merged into the "beta" branch when they're stable enough, and then be merged into the "main" branch when they're ready to be live and are well-tested. Builds of the "dev" branch could occur daily (by implementing Github Actions), "beta" could occur weekly, and "main" could occur whenever a hotfix is ready or whenever it's time for a new build.
Beta Was this translation helpful? Give feedback.
All reactions