diff options
| author | Robert Speicher <rspeicher@gmail.com> | 2016-03-24 18:02:13 -0400 |
|---|---|---|
| committer | Robert Speicher <rspeicher@gmail.com> | 2016-03-24 18:03:06 -0400 |
| commit | 6abcb8820de24ca817c2b0258010e0a79a0ffe81 (patch) | |
| tree | 0cdf0577cfe2e5ae905160945549c621d5021c09 /doc/release/howto_rc1.md | |
| parent | 3028a7d25a88ccf7352eec2a7238fe555cc770e1 (diff) | |
| download | gitlab-ce-rs-remove-release-docs.tar.gz | |
Remove release docs from the CE repositoryrs-remove-release-docs
More detailed, updated, and accurate versions of these docs now live in
https://gitlab.com/gitlab-org/release-tools
[ci skip]
Diffstat (limited to 'doc/release/howto_rc1.md')
| -rw-r--r-- | doc/release/howto_rc1.md | 55 |
1 files changed, 0 insertions, 55 deletions
diff --git a/doc/release/howto_rc1.md b/doc/release/howto_rc1.md deleted file mode 100644 index 07c703142d4..00000000000 --- a/doc/release/howto_rc1.md +++ /dev/null @@ -1,55 +0,0 @@ -# How to create RC1 - -The RC1 release comes with the task to update the installation and upgrade docs. Be mindful that there might already be merge requests for this on GitLab or GitHub. - -### 1. Update the installation guide - -1. Check if it references the correct branch `x-x-stable` (doesn't exist yet, but that is okay) -1. Check the [GitLab Shell version](/lib/tasks/gitlab/check.rake#L782) -1. Check the [Git version](/lib/tasks/gitlab/check.rake#L794) -1. There might be other changes. Ask around. - -### 2. Create update guides - -[Follow this guide](howto_update_guides.md) to create update guides. - -### 3. Code quality indicators - -Make sure the code quality indicators are green / good. - -- [](http://ci.gitlab.org/projects/1?ref=master) on ci.gitlab.org (master branch) - -- [](https://semaphoreapp.com/gitlabhq/gitlabhq) (master branch) - -- [](https://codeclimate.com/github/gitlabhq/gitlabhq) - -- [](https://gemnasium.com/gitlabhq/gitlabhq) this button can be yellow (small updates are available) but must not be red (a security fix or an important update is available) - -- [](https://coveralls.io/r/gitlabhq/gitlabhq) - -### 4. Run release tool - -**Make sure EE `master` has latest changes from CE `master`** - -Get release tools - -``` -git clone git@dev.gitlab.org:gitlab/release-tools.git -cd release-tools -``` - -Release candidate creates stable branch from master. -So we need to sync master branch between all CE, EE and CI remotes. - -``` -bundle exec rake sync -``` - -Create release candidate and stable branch: - -``` -bundle exec rake release["x.x.0.rc1"] -``` - -Now developers can use master for merging new features. -So you should use stable branch for future code changes related to release. |