diff options
author | Mike Lewis <mlewis@gitlab.com> | 2019-02-14 15:40:57 +0000 |
---|---|---|
committer | Mike Lewis <mlewis@gitlab.com> | 2019-02-14 15:40:57 +0000 |
commit | a2449492d0fd3f41abb86204ebbcd221b4aa994a (patch) | |
tree | a818f4f358a46c74b84fe8bc88a26d678aa05543 | |
parent | 23b781057bb5bc5ea9b7c6abb87b7cad0db28793 (diff) | |
download | gitlab-ce-a2449492d0fd3f41abb86204ebbcd221b4aa994a.tar.gz |
Add better links on documentation process to PROCESS.md
-rw-r--r-- | PROCESS.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/PROCESS.md b/PROCESS.md index 74b8440bc56..ad74ead8aab 100644 --- a/PROCESS.md +++ b/PROCESS.md @@ -156,12 +156,12 @@ on behalf of the community member. Every new feature or change should be shipped with its corresponding documentation in accordance with the -[documentation process](https://docs.gitlab.com/ee/development/documentation/workflow.html) +[documentation process](https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html) and [structure](https://docs.gitlab.com/ee/development/documentation/structure.html) guides. Note that a technical writer will review all changes to documentation. This can occur -in the same MR as the feature code, but if there is not sufficient time, it can -be planned via a follow-up issue for doc review, and another MR if needed. -Regardless, complete docs must be merged with code by the freeze. +in the same MR as the feature code, but [if there is not sufficient time or need, +it can be planned via a follow-up issue for doc review](https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#1-product-managers-role), +and another MR, if needed. Regardless, complete docs must be merged with code by the freeze. #### What happens if these deadlines are missed? |