From 020a4dc81e7ecfa8529853de0c12ef9d86272300 Mon Sep 17 00:00:00 2001 From: Ingo Schommer Date: Tue, 17 Jan 2017 11:51:20 +1300 Subject: [PATCH] Removed "release maintainer" from docs The role moves around based on current availability. @tractorcow has done most of the last releases, but a separate team (headed by @dhensby) will be responsible for 3.x releases. There's not really much point to declaring a release maintainer, unless there's disagreements in the core team where we need an arbitrator. So far those conflicts have been resolved on individual tickets (e.g. what should go into a release), and the process for that seems to work well. --- docs/en/05_Contributing/04_Release_Process.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/en/05_Contributing/04_Release_Process.md b/docs/en/05_Contributing/04_Release_Process.md index e91c1d902..5f0d73860 100644 --- a/docs/en/05_Contributing/04_Release_Process.md +++ b/docs/en/05_Contributing/04_Release_Process.md @@ -4,10 +4,6 @@ summary: Describes the process followed for "core" releases. This page describes the process followed for "core" releases (mainly the `framework` and `cms` modules). -## Release Maintainer - -The current maintainer responsible for planning and performing releases is Ingo Schommer (ingo at silverstripe dot com). - ## Release Planning Our most up-to-date release plans are typically in the ["framework" milestone](https://github.com/silverstripe/silverstripe-framework/milestones) and ["cms" milestone](https://github.com/silverstripe/silverstripe-cms/milestones).