Commit 9b8ee3e0a6c31a430988cd5d397a8baa41d4533a

Authored by Sytse Sijbrandij
2 parents 36ea8645 369bd858

Merge branch 'advise-in-upgrade-guide-is-outdated' into 'master'

Advise In Upgrade Guide Is Outdated
doc/update/4.2-to-5.0.md
1 1 # From 4.2 to 5.0
2 2  
3 3 ## Warning
4   -GitLab 5.0 is affected by critical security vulnerability CVE-2013-4490. Please update to GitLab 5.4 immediately.
  4 +GitLab 5.0 is affected by critical security vulnerability CVE-2013-4490.
5 5  
6 6 ## Important changes
7 7  
... ...
doc/update/5.0-to-5.1.md
1 1 # From 5.0 to 5.1
2 2  
3 3 ## Warning
4   -GitLab 5.1 is affected by critical security vulnerability CVE-2013-4490. Please [update to GitLab 5.4 immediately](5.1-to-5.4.md).
  4 +GitLab 5.1 is affected by critical security vulnerability CVE-2013-4490.
5 5  
6 6 ## Release notes:
7 7  
... ...
doc/update/5.1-to-5.2.md
1 1 # From 5.1 to 5.2
2 2  
3 3 ## Warning
4   -GitLab 5.2 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489. Please [update to GitLab 5.4 directly](5.1-to-5.4.md).
  4 +GitLab 5.2 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
5 5  
6 6 ### 0. Backup
7 7  
... ...
doc/update/5.1-to-5.4.md
1 1 # From 5.1 to 5.4
2 2 Also works starting from 5.2.
3 3  
4   -## Notice
5   -Security vulnerabilities CVE-2013-4490 and CVE-2013-4489 have been patched in the latest version of GitLab 5.4.
6   -
7 4 ### 0. Backup
8 5  
9 6 It's useful to make a backup just in case things go south:
... ...
doc/update/5.1-to-6.0.md
1 1 # From 5.1 to 6.0
2 2  
3 3 ## Warning
4   -GitLab 6.0 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489. Please [update to GitLab 6.2 immediately](6.0-to-6.2.md).
  4 +GitLab 6.0 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
5 5  
6 6 ### Deprecations
7 7  
... ...
doc/update/5.2-to-5.3.md
1 1 # From 5.2 to 5.3
2 2  
3 3 ## Warning
4   -GitLab 5.3 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489. Please [update to GitLab 5.4 directly](5.1-to-5.4.md).
  4 +GitLab 5.3 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
5 5  
6 6 ### 0. Backup
7 7  
... ...
doc/update/5.3-to-5.4.md
1 1 # From 5.3 to 5.4
2 2  
3   -## Notice
4   -Security vulnerabilities CVE-2013-4490 and CVE-2013-4489 have been patched in the latest version of GitLab 5.4.
5   -
6 3 ### 0. Backup
7 4  
8 5 It's useful to make a backup just in case things go south:
... ...
doc/update/5.4-to-6.0.md
1 1 # From 5.4 to 6.0
2 2  
3 3 ## Warning
4   -GitLab 6.0 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489. Please [update to GitLab 6.2 immediately](6.0-to-6.2.md).
  4 +GitLab 6.0 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
5 5  
6 6 ### Deprecations
7 7  
... ...
doc/update/6.0-to-6.1.md
1 1 # From 6.0 to 6.1
2 2  
3 3 ## Warning
4   -GitLab 6.1 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489. Please [update to GitLab 6.2 directly](6.0-to-6.2.md).
  4 +GitLab 6.1 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489.
5 5  
6 6 # In 6.1 we remove a lot of deprecated code.
7 7 # You should update to 6.0 before installing 6.1 so all the necessary conversions are run.
... ...
doc/update/6.1-to-6.2.md
1 1 # From 6.1 to 6.2
2 2  
3   -## Notice
4   -Security vulnerabilities CVE-2013-4490 and CVE-2013-4489 have been patched in the latest version of GitLab 6.2.
5   -
6 3 # You should update to 6.1 before installing 6.2 so all the necessary conversions are run.
7 4  
8 5 ### 0. Backup
... ...