Repository Layout
In order to avoid turning the repositories into a messy heap of branches we try to adhere to a certain naming convention for the branches.
| Branch Name | Purpose |
|---|---|
| master | Main development branch |
| release | Current release branch |
| releases/<x.y>[-<suffix>] | Release branch for the given DUNE version. The version should start with the numeric version of the release (e.g. “2.2”), followed by an optional suffix, e.g. “2.2-cmake”. Keeping the numbers up front makes for better ordering of the releases in listings. |
| feature/<name> | Feature branch Please use descriptive names. For consistency, I suggest joining words with dashes, not underscores. Examples: feature/cmake feature/dynamic-geometry-initialization |
| p/<username>/<whatever> | Personal branch of user usernameThis personal namespace provides users with an easy way to share ideas and transfer code between computers. Branches in this namespace are globally readable, but can only be written to by their owner. Commits to these branches will not be announced on the mailing list. |
| v<x.y.z> | Annotated release tag for the given DUNE version. Starting with the 2.1 series, triplets are always used for release tags, even for the initial release (e.g. v2.2.0). |
|
Legal Statements / Impressum |
Hosted by TU Dresden & Uni Heidelberg |
generated with Hugo v0.131.0
(Oct 16, 22:23, 2026)