From 468d2667cf9c12ac43bf7f12a67053d0ed9344f3 Mon Sep 17 00:00:00 2001 From: Evan Read Date: Thu, 12 Sep 2019 14:24:51 +1000 Subject: Introduce Tech Writing Team label to process --- doc/development/documentation/feature-change-workflow.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/development/documentation') diff --git a/doc/development/documentation/feature-change-workflow.md b/doc/development/documentation/feature-change-workflow.md index 38ccae41df4..29d66689e92 100644 --- a/doc/development/documentation/feature-change-workflow.md +++ b/doc/development/documentation/feature-change-workflow.md @@ -77,7 +77,7 @@ and default merge request template will assist you with following this process. For issues requiring any new or updated documentation, the Product Manager (PM) must: -- Add the `Documentation` label. +- Add the ~documentation label. - Confirm or add the [documentation requirements](#documentation-requirements-in-feature-issues). - Ensure the issue contains any new or updated feature name, overview/description, and use cases, as required per the [documentation structure and template](structure.md), when applicable. @@ -92,7 +92,7 @@ do the following: #### Authoring -As a developer, if a ~feature issue also contains the ~Documentation label, you must ship the new or updated documentation with the code of the feature. The documentation is an essential part of the product. +As a developer, if a ~feature issue also contains the ~documentation label, you must ship the new or updated documentation with the code of the feature. The documentation is an essential part of the product. Technical writers are happy to help, as requested and planned on an issue-by-issue basis. For feature issues requiring documentation, follow the process below unless otherwise agreed with the product manager and technical writer for a given issue: -- cgit v1.2.1