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
Tatuya Kamada
gitlab-ce
Commits
4e3bf439
Commit
4e3bf439
authored
Nov 24, 2014
by
Jacob Vosmaer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Establish ownership of security releases
parent
e0c870c0
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
3 additions
and
0 deletions
+3
-0
doc/release/patch.md
doc/release/patch.md
+1
-0
doc/release/security.md
doc/release/security.md
+2
-0
No files found.
doc/release/patch.md
View file @
4e3bf439
...
@@ -17,6 +17,7 @@ Otherwise include it in the monthly release and note there was a regression fix
...
@@ -17,6 +17,7 @@ Otherwise include it in the monthly release and note there was a regression fix
1.
Create an issue on private GitLab development server
1.
Create an issue on private GitLab development server
1.
Name the issue "Release X.X.X CE and X.X.X EE", this will make searching easier
1.
Name the issue "Release X.X.X CE and X.X.X EE", this will make searching easier
1.
Fix the issue on a feature branch, do this on the private GitLab development server
1.
Fix the issue on a feature branch, do this on the private GitLab development server
1.
If it is a security issue, then assign it to the release manager and apply a 'security' label
1.
Consider creating and testing workarounds
1.
Consider creating and testing workarounds
1.
After the branch is merged into master, cherry pick the commit(s) into the current stable branch
1.
After the branch is merged into master, cherry pick the commit(s) into the current stable branch
1.
Make sure that the build has passed and all tests are passing
1.
Make sure that the build has passed and all tests are passing
...
...
doc/release/security.md
View file @
4e3bf439
...
@@ -14,7 +14,9 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c
...
@@ -14,7 +14,9 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c
1.
Verify that the issue can be reproduced
1.
Verify that the issue can be reproduced
1.
Acknowledge the issue to the researcher that disclosed it
1.
Acknowledge the issue to the researcher that disclosed it
1.
Inform the release manager that there needs to be a security release
1.
Do the steps from
[
patch release document
](
doc/release/patch.md
)
, starting with "Create an issue on private GitLab development server"
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.
Create feature branches for the blog post on GitLab.com and link them from the code branch
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.
Merge and publish the blog posts
1.
Send tweets about the release from
`@gitlabhq`
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