From 913fb0f876f2170bd537b5eaa4648315b7d59a46 Mon Sep 17 00:00:00 2001 From: Dan Untenzu Date: Tue, 24 Jan 2017 10:51:19 +0100 Subject: [PATCH] [FEATURE] Docs: Explain branches Explain master and next-release branch. Master should always be a live version only, unless the version is changed to something like "2.0.0-dev". Refs # --- CONTRIBUTING.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 8c6752e..641fb44 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -61,8 +61,16 @@ Translation may be add via [Jirafeau's Weblate](https://hosted.weblate.org/proje The whole project is not clean about that yet, feel free to fix :) +## Branches + +* ```master``` = latest release, e.g. 2.0.1 +* ```next-release``` = development branch - all new features are merged into this branch until the next version is released. So use this branch as base while developing new features or bugfixes. +* ```test``` = sandbox branch to test new features or merge requests, or run integration tests. The content of this branch may change at any time. + ## Merge Requests Please create one branch for each feature and send one merge request for each branch. Dont squash several changes or commits into one merge request as this is hard to review. + +Please use ```next-release``` as base branch and send your merge request to this branch (not ```master```). -- 2.34.1