Skip to content

Propose a common branching strategy for all community repositories #150

@e-backmark-ericsson

Description

@e-backmark-ericsson

Description

In order for not re-inventing the wheel I believe it would be good to document a best practice on what branching strategy to use in the Eiffel Community repositories. It should not be mandatory to follow it, but it should be recommended. An example of a branching strategy is currently being discussed through this issue: eiffel-community/eiffel-remrem-semantics#148. That could serve as one alternative when defining a common proposed branching strategy for our repositories.

Motivation

Easier to navigate the Eiffel Community repositories if most of them use the same branching strategy.

Exemplification

Less startup time when initiating a new repository and less frustration when the recommended branching strategy is not defined.

Benefits

See Motivation

Possible Drawbacks

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions