Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
2f66d23d
Commit
2f66d23d
authored
Feb 14, 2019
by
Mike Lewis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typo and updatee tech writer planning section
parent
e1a1ca0e
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/development/documentation/feature-change-workflow.md
doc/development/documentation/feature-change-workflow.md
+2
-2
No files found.
doc/development/documentation/feature-change-workflow.md
View file @
2f66d23d
...
...
@@ -146,9 +146,9 @@ Any party can raise the item to the PM for review at any point: the dev, the tec
#### Planning
-
The technical writer monitors the documentation needs of issues assigned to the current and next milestone
for their DevOps stage(s), and participates in any needed discussion on docs planning
for their DevOps stage(s), and participates in any needed discussion on docs planning
and requirements refinement
with the dev, PM, and others.
-
The technical writer will review these again upon the kickoff and provide feedback, as needed.
-
The technical writer will review these
requirements
again upon the kickoff and provide feedback, as needed.
This is not a blocking review and developers should not wait to work on docs.
#### Collaboration
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment