-
Notifications
You must be signed in to change notification settings - Fork 9
Home
ru37z edited this page Dec 3, 2021
·
5 revisions
Welcome to the SOCBED wiki!
- New features, fixes, etc., MUST be created as separate feature branches and then merged into the development branch (
dev
) via pull request (with merge commit) by a maintainer. - When the
dev
pipelines (unit tests and nightly build with system tests) pass, thedev
branch CAN be merged intomain
via pull request (with merge commit). This is usually done when the new features or bug fixes indev
are a significant improvement over themain
branch for SOCBED users. - After merging into
main
, a new release MUST be created with a tag name following the semantic versioning scheme (i.e.,vX.Y.Z
, where Y is incremented on new features and Z is incremented if only bugs are fixed). The release title MUST beSOCBED <tag>
, e.g.,SOCBED v1.0.0
. The release description MUST include the significant changes as bullet-point list.