Update release docs to deploy to GitLab.com before publishing.
This commit is contained in:
parent
e6c5a8b161
commit
90a308ea00
|
@ -18,6 +18,7 @@ Otherwise include it in the monthly release and note there was a regression fix
|
||||||
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. If it is a security issue, then assign it to the release manager and apply a 'security' label
|
||||||
|
1. Build the package for GitLab.com and do a deploy
|
||||||
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
|
||||||
|
|
|
@ -17,6 +17,7 @@ Please report suspected security vulnerabilities in private to <support@gitlab.c
|
||||||
1. Inform the release manager that there needs to be a security release
|
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. 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 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`
|
||||||
|
|
Loading…
Reference in New Issue