Skip to content

Home

Jump to bottom
ru37z edited this page Dec 3, 2021 · 5 revisions

Welcome to the SOCBED wiki!

Development Workflow

  • New features, fixes, etc., MUST be created as separate branches and then merged into the dev branch via pull request by a maintainer.
  • When the dev pipelines (unit tests and nightly build with system tests) pass, the main branch CAN be fast-forwarded to the dev branch (i.e., without a merge commit). This is usually done when the new features or bug fixes in dev are a significant improvement over the main branch for SOCBED users.
  • After fast-forwarding 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 ate fixed). The description of the release MUST summarize the significant changes. The release title SHOULD be left empty (GitHub then uses the tag as title).
Clone this wiki locally