openstack
/
project-team-guide
Code Issues Proposed changes

There are no core developers, only core reviewers 

We've insisted in the past that "core developers" aren't a thing, so
if we want to avoid continued propagation of that terminology then
we should do our best to eradicate it in official documents.

Change-Id: Ia26a2cf9b6bf706162641b4b8d4e6e5c2f9e992a
This commit is contained in:
Jeremy Stanley 2018-06-28 14:25:50 +00:00
parent 58ce3837a7
commit 1f8211d041
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/bugs.rst
View File

@ -150,7 +150,7 @@ indeed a valid bug), you should set:
* Status: `Confirmed`
If you're a core developer or a member of the project bug supervision team,
If you're a core reviewer or a member of the project bug supervision team,
you should also prioritize the bug:
* Importance: <Bug impact> (see above)
@ -163,7 +163,7 @@ solution in the comments. Sometimes the implementation of the fix will be
straightforward and you would jump directly to bugfixing, but in some other
cases, you would just post your complete debugging analysis and give someone
else the opportunity of fixing the bug. Then you should ask a core
developer or bug supervisor to set:
reviewer or bug supervisor to set:
* Status: `Triaged`

2
doc/source/stable-branches.rst
View File

@ -267,7 +267,7 @@ If unsure if a fix is appropriate for the stable branch, project-specific
stable maintenance team members should seek stable maintenance core team
members opinion.
Existing core developers are greatly encouraged to join the stable maintenance
Existing core reviewers are greatly encouraged to join the stable maintenance
teams in order to help with reviewing backports, judging their appropriateness
for the stable branch and approving them.