BigW Consortium Gitlab
Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
G
gitlab-ce
Project
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Forest Godfrey
gitlab-ce
Commits
c93f4662
Commit
c93f4662
authored
Feb 09, 2015
by
Dmitriy Zaporozhets
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Extract update guide to separate doc to prevent mess
parent
bd19bce3
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
56 additions
and
53 deletions
+56
-53
howto_rc1.md
doc/release/howto_rc1.md
+1
-53
howto_update_guides.md
doc/release/howto_update_guides.md
+55
-0
No files found.
doc/release/howto_rc1.md
View file @
c93f4662
...
...
@@ -11,59 +11,7 @@ The RC1 release comes with the task to update the installation and upgrade docs.
### 2. Create update guides
1.
Create: CE update guide from previous version. Like
`7.3-to-7.4.md`
1.
Create: CE to EE update guide in EE repository for latest version.
1.
Update:
`6.x-or-7.x-to-7.x.md`
to latest version.
1.
Create: CI update guide from previous version
It's best to copy paste the previous guide and make changes where necessary.
The typical steps are listed below with any points you should specifically look at.
#### 0. Any major changes?
List any major changes here, so the user is aware of them before starting to upgrade. For instance:
-
Database updates
-
Web server changes
-
File structure changes
#### 1. Stop server
#### 2. Make backup
#### 3. Do users need to update dependencies like `git`?
-
Check if the
[
GitLab Shell version
](
/lib/tasks/gitlab/check.rake#L782
)
changed since the last release.
-
Check if the
[
Git version
](
/lib/tasks/gitlab/check.rake#L794
)
changed since the last release.
#### 4. Get latest code
#### 5. Does GitLab shell need to be updated?
#### 6. Install libs, migrations, etc.
#### 7. Any config files updated since last release?
Check if any of these changed since last release:
-
[
lib/support/nginx/gitlab
](
/lib/support/nginx/gitlab
)
-
[
lib/support/nginx/gitlab-ssl
](
/lib/support/nginx/gitlab-ssl
)
-
<https://gitlab.com/gitlab-org/gitlab-shell/commits/master/config.yml.example>
-
[
config/gitlab.yml.example
](
/config/gitlab.yml.example
)
-
[
config/unicorn.rb.example
](
/config/unicorn.rb.example
)
-
[
config/database.yml.mysql
](
/config/database.yml.mysql
)
-
[
config/database.yml.postgresql
](
/config/database.yml.postgresql
)
-
[
config/initializers/rack_attack.rb.example
](
/config/initializers/rack_attack.rb.example
)
-
[
config/resque.yml.example
](
/config/resque.yml.example
)
#### 8. Need to update init script?
Check if the
`init.d/gitlab`
script changed since last release:
[
lib/support/init.d/gitlab
](
/lib/support/init.d/gitlab
)
#### 9. Start application
#### 10. Check application status
[
Follow this guide
](
howto_update_guides.md
)
to create update guides.
### 3. Code quality indicators
...
...
doc/release/howto_update_guides.md
0 → 100644
View file @
c93f4662
# Create update guides
1.
Create: CE update guide from previous version. Like
`7.3-to-7.4.md`
1.
Create: CE to EE update guide in EE repository for latest version.
1.
Update:
`6.x-or-7.x-to-7.x.md`
to latest version.
1.
Create: CI update guide from previous version
It's best to copy paste the previous guide and make changes where necessary.
The typical steps are listed below with any points you should specifically look at.
#### 0. Any major changes?
List any major changes here, so the user is aware of them before starting to upgrade. For instance:
-
Database updates
-
Web server changes
-
File structure changes
#### 1. Stop server
#### 2. Make backup
#### 3. Do users need to update dependencies like `git`?
-
Check if the
[
GitLab Shell version
](
/lib/tasks/gitlab/check.rake#L782
)
changed since the last release.
-
Check if the
[
Git version
](
/lib/tasks/gitlab/check.rake#L794
)
changed since the last release.
#### 4. Get latest code
#### 5. Does GitLab shell need to be updated?
#### 6. Install libs, migrations, etc.
#### 7. Any config files updated since last release?
Check if any of these changed since last release:
-
[
lib/support/nginx/gitlab
](
/lib/support/nginx/gitlab
)
-
[
lib/support/nginx/gitlab-ssl
](
/lib/support/nginx/gitlab-ssl
)
-
<https://gitlab.com/gitlab-org/gitlab-shell/commits/master/config.yml.example>
-
[
config/gitlab.yml.example
](
/config/gitlab.yml.example
)
-
[
config/unicorn.rb.example
](
/config/unicorn.rb.example
)
-
[
config/database.yml.mysql
](
/config/database.yml.mysql
)
-
[
config/database.yml.postgresql
](
/config/database.yml.postgresql
)
-
[
config/initializers/rack_attack.rb.example
](
/config/initializers/rack_attack.rb.example
)
-
[
config/resque.yml.example
](
/config/resque.yml.example
)
#### 8. Need to update init script?
Check if the
`init.d/gitlab`
script changed since last release:
[
lib/support/init.d/gitlab
](
/lib/support/init.d/gitlab
)
#### 9. Start application
#### 10. Check application status
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