summaryrefslogtreecommitdiff
path: root/doc/release/security.md
diff options
context:
space:
mode:
authordosire <sytses@gmail.com>2014-04-03 10:09:52 +0200
committerdosire <sytses@gmail.com>2014-04-03 10:09:52 +0200
commit770747af68b82642fa98e69c79c9574321504167 (patch)
tree1c7bb929745811ee5fec70855d176ed3c00e206e /doc/release/security.md
parentca1d31f8cdd111c79f547b2e511f478d8f15696e (diff)
downloadgitlab-ce-770747af68b82642fa98e69c79c9574321504167.tar.gz
Specify that the tag should be annotated.
Diffstat (limited to 'doc/release/security.md')
-rw-r--r--doc/release/security.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/release/security.md b/doc/release/security.md
index 8e5a7e32099..56a44b5d1da 100644
--- a/doc/release/security.md
+++ b/doc/release/security.md
@@ -18,7 +18,7 @@ Please report suspected security vulnerabilities in private to support@gitlab.co
1. Create feature branches for the blog post on GitLab.com and link them from the code branch
1. Merge the code feature branch into master
1. Cherry-pick the code into the latest stable branch
-1. Create a git tag vX.X.X for CE and another patch release for EE
+1. Create an annotated tag vX.X.X for CE and another patch release for EE
1. Push the code and the tags to all the CE and EE repositories
1. Apply the patch to GitLab Cloud and the private GitLab development server
1. Merge and publish the blog posts