=link_toproject_note_path(@project,note),title: "Remove comment",method: :delete,data: {confirm: 'Are you sure you want to remove this comment?'},remote: true,class: "danger js-note-delete"do
=link_toproject_note_path(@project,note),title: "Remove comment",method: :delete,data: {confirm: 'Are you sure you want to remove this comment?'},remote: true,class: "danger js-note-delete"do
Follow the [release doc in the Omnibus repository](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md).
This can happen before tagging because Omnibus uses tags in its own repo and SHA1's to refer to the GitLab codebase.
### **4. Create annotated tag vx.x.x**
In `x-x-stable` branch check for the SHA-1 of the commit with VERSION file changed. Tag that commit,
In `x-x-stable` branch check for the SHA-1 of the commit with VERSION file changed. Tag that commit,
...
@@ -244,12 +239,17 @@ git tag -a vx.x.0 -m 'Version x.x.0' xxxxx
...
@@ -244,12 +239,17 @@ git tag -a vx.x.0 -m 'Version x.x.0' xxxxx
where `xxxxx` is SHA-1.
where `xxxxx` is SHA-1.
### **5. Push the tag**
### **4. Push the tag**
```
```
git push origin vx.x.0
git push origin vx.x.0
```
```
### **5. Build the Omnibus packages**
Follow the [release doc in the Omnibus repository](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/doc/release.md).
This can happen before tagging because Omnibus uses tags in its own repo and SHA1's to refer to the GitLab codebase.
### **6. Push to remotes**
### **6. Push to remotes**
For GitLab CE, push to dev, GitLab.com and GitHub.
For GitLab CE, push to dev, GitLab.com and GitHub.
...
@@ -258,8 +258,6 @@ For GitLab EE, push to the subscribers repo.
...
@@ -258,8 +258,6 @@ For GitLab EE, push to the subscribers repo.
Make sure the branch is marked 'protected' on each of the remotes you pushed to.
Make sure the branch is marked 'protected' on each of the remotes you pushed to.
NOTE: You might not have the rights to push to master on dev. Ask Dmitriy.
### **7. Publish blog for new release**
### **7. Publish blog for new release**
Merge the [blog merge request](#1-prepare-the-blog-post) in `www-gitlab-com` repository.
Merge the [blog merge request](#1-prepare-the-blog-post) in `www-gitlab-com` repository.
...
@@ -280,6 +278,10 @@ Include a link to the blog post and keep it short.
...
@@ -280,6 +278,10 @@ Include a link to the blog post and keep it short.
Proposed email text:
Proposed email text:
"We have released a new version of GitLab. See our blog post(<link>) for more information."
"We have released a new version of GitLab. See our blog post(<link>) for more information."
### **10. Update installation.md**
Update [installation.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md) to the newest version in master and cherry-pick that commit into the stable branch.
@@ -21,7 +21,7 @@ If you have local changes to your GitLab repository the script will stash them a
...
@@ -21,7 +21,7 @@ If you have local changes to your GitLab repository the script will stash them a
## 2. Run GitLab upgrade tool
## 2. Run GitLab upgrade tool
Note: GitLab 7.2 adds cmake as dependency. Please check the dependencies in the [installation guide.](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md#1-packages-dependencies)
Note: GitLab 7.2 adds `pkg-config` and `cmake` as dependency. Please check the dependencies in the [installation guide.](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md#1-packages-dependencies)
# Starting with GitLab version 7.0 upgrader script has been moved to bin directory
# Starting with GitLab version 7.0 upgrader script has been moved to bin directory