Skip to content

Problem: Project shall have one branch, master, and no topic branches #45

Description

@weex

Since this was forked from upstream, we haven't removed all the extra branches but quoting C4:

2.5. Branches and Releases

  1. The project SHALL have one branch ("master") that always holds the latest in-progress version and SHOULD always build.
  2. The project SHALL NOT use topic branches for any reason. Personal forks MAY use topic branches.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions