Tagging and branching conventions

[AFoletti]

I am referring here to Steven's branch about naming conventions since we discussed but we just came to the conclusion that the branch will not be merged nor deleted, leaving the issue in kind of a limbo.

My goal with this issue is to open a discussion and eventually to achieve a decision resulting in an action.

My 2 cents:

• we all agreed upon the need of naming convention to keep some order. This makes in my opinion Steven's work in the referenced branch very much valuable and we should not discard it that easily.
• I am really convinced that the "tag" part of Steven's proposal (up to this line) is 100% spot on and should be merged/implemented. I would just add a requirement, for the "consultation" releases, to tick the "pre-release" box as in the picture

• for the "work in progress" part, I would like to suggest to switch from branching naming convention (which is rigid and honestly not very useful since you cannot filter for that) to work with a combination of Labels ("Feature", "Improvement" and "Fix" as suggested by Steven) and Milestones (referencing the projected release the change will be integrated into).
  Moving this to Labels/Milestones will allow for a much more flexible management and the ability to filter issues and PR per change type and milestone, allowing for a better overview.

Up for discussion @hurni , @montanajava , @lars-steffen

[montanajava]

Issue still open: Need to adjust based on input from Ambrogio.