tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Removed "release maintainer" from docs

Browse Source 
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.
This commit is contained in:
Ingo Schommer 2017-01-17 11:51:20 +13:00
parent 68c2bc6158
commit 020a4dc81e
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/en/05_Contributing/04_Release_Process.md
View File

@ -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).