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
iv
gitlab-ce
Commits
66384d7d
Commit
66384d7d
authored
Mar 11, 2015
by
Marin Jankovski
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add a note about building AMI to security doc
parent
536d4373
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
0 deletions
+1
-0
doc/release/security.md
doc/release/security.md
+1
-0
No files found.
doc/release/security.md
View file @
66384d7d
...
...
@@ -18,6 +18,7 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c
1.
Do the steps from
[
patch release document
](
doc/release/patch.md
)
, starting with "Create an issue on private GitLab development server"
1.
The MR with the security fix should get a 'security' label and be assigned to the release manager
1.
Build the package for GitLab.com and do a deploy
1.
[
Create new AMIs
](
https://dev.gitlab.org/gitlab/AMI/blob/master/README.md
)
1.
Create feature branches for the blog post on GitLab.com and link them from the code branch
1.
Merge and publish the blog posts
1.
Send tweets about the release from
`@gitlabhq`
...
...
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