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
15d08049
Commit
15d08049
authored
May 07, 2018
by
James Lopez
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update Security Developer Workflow.md
parent
eaeeac2f
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
.gitlab/issue_templates/Security Developer Workflow.md
.gitlab/issue_templates/Security Developer Workflow.md
+2
-2
No files found.
.gitlab/issue_templates/Security Developer Workflow.md
View file @
15d08049
...
...
@@ -28,11 +28,11 @@ Set the title to: `[Security] Description of the original issue`
-
[ ] Add the ~security label and prefix with the version
`WIP: [X.Y]`
the title of the MR
-
[
] Make sure all MRs have a link in the [links section
](
#links
)
and are assigned to a Release Manager.
[
seckpick documentation
]:
https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/
process
.md#secpick-script
[
seckpick documentation
]:
https://gitlab.com/gitlab-org/release/docs/blob/master/general/security/
developer
.md#secpick-script
#### Documentation and final details
-
[
] Check the topic on #security to see when the next release is going
ot
happen and add a link to the [links section
](
#links
)
-
[
] Check the topic on #security to see when the next release is going
to
happen and add a link to the [links section
](
#links
)
-
[
] Find out the versions affected (the Git history of the files affected may help you with this) and add them to the [details section
](
#details
)
-
[
] Fill in any upgrade notes that users may need to take into account in the [details section
](
#details
)
-
[
] Add Yes/No and further details if needed to the migration and settings columns in the [details section
](
#details
)
...
...
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