From d97adf814ac1bda2894e259a3cb998523c741027 Mon Sep 17 00:00:00 2001
From: Axel Huebl <axel.huebl@plasma.ninja>
Date: Wed, 10 Feb 2021 17:57:38 -0800
Subject: [PATCH] Docs: dev-centered development (#928)

We only use a `dev` branch for all development and occationally open
`release-X.Y.Z` branches to backport features to prior releases.
---
 CONTRIBUTING.rst                  | 1 -
 docs/source/dev/repostructure.rst | 1 -
 2 files changed, 2 deletions(-)

diff --git a/CONTRIBUTING.rst b/CONTRIBUTING.rst
index 80e9566a28..9acba1d287 100644
--- a/CONTRIBUTING.rst
+++ b/CONTRIBUTING.rst
@@ -12,7 +12,6 @@ For existing tasks, the labels `good first issue <https://github.com/openPMD/ope
 In case you want to start working on one of those, just *comment* in it first so no work is duplicated.
 
 New contributions in form of `pull requests <https://help.github.com/articles/about-pull-requests/>`_ always need to go in the ``dev`` (development) branch.
-The ``master`` branch contains the last stable release and receives updates only when a new version is drafted.
 
 Maintainers organize prioritites and progress in the `projects tab <https://github.com/openPMD/openPMD-api/projects>`_.
 
diff --git a/docs/source/dev/repostructure.rst b/docs/source/dev/repostructure.rst
index 4f5a92ff63..aaaff75932 100644
--- a/docs/source/dev/repostructure.rst
+++ b/docs/source/dev/repostructure.rst
@@ -6,7 +6,6 @@ Repository Structure
 Branches
 --------
 
-* ``master``: the latest stable release, always tagged with a version
 * ``dev``: the development branch where all features start from and are merged to
 * ``release-X.Y.Z``: release candidate for version ``X.Y.Z`` with an upcoming release, receives updates for bug fixes and documentation such as change logs but usually no new features