Software Publico / Gitlab

Authored by Jacob Vosmaer 2013-11-02 16:49:26 +0100

1 parent 9e31555a

Exists in master and in 4 other branches

Showing 9 changed files with 27 additions and 0 deletions Show diff stats

doc/update/4.2-to-5.0.md

1	# From 4.2 to 5.0	1	# From 4.2 to 5.0
2		2
		3	+## Warning
		4	+GitLab 5.0 is affected by critical security vulnerability CVE-2013-4490. Please update to GitLab 5.4 immediately.
		5	+
3	## Important changes	6	## Important changes
4		7
5	* We don't use `gitlab` user any more. Everything will be moved to `git` user	8	* We don't use `gitlab` user any more. Everything will be moved to `git` user

doc/update/5.0-to-5.1.md

1	# From 5.0 to 5.1	1	# From 5.0 to 5.1
2		2
		3	+## Warning
		4	+GitLab 5.1 is affected by critical security vulnerability CVE-2013-4490. Please update to GitLab 5.4 immediately.
		5	+
3	## Release notes:	6	## Release notes:
4		7
5	* `unicorn` replaced with `puma`	8	* `unicorn` replaced with `puma`

doc/update/5.1-to-5.2.md

1	# From 5.1 to 5.2	1	# From 5.1 to 5.2
2		2
		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 immediately.
		5	+
3	### 0. Backup	6	### 0. Backup
4		7
5	It's useful to make a backup just in case things go south:	8	It's useful to make a backup just in case things go south:

doc/update/5.1-to-6.0.md

1	# From 5.1 to 6.0	1	# From 5.1 to 6.0
2		2
		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 or newer immediately.
		5	+
3	### Deprecations	6	### Deprecations
4		7
5	#### Global projects	8	#### Global projects

doc/update/5.2-to-5.3.md

1	# From 5.2 to 5.3	1	# From 5.2 to 5.3
2		2
		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 immediately.
		5	+
3	### 0. Backup	6	### 0. Backup
4		7
5	It's useful to make a backup just in case things go south:	8	It's useful to make a backup just in case things go south:

doc/update/5.3-to-5.4.md

1	# From 5.3 to 5.4	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	+
3	### 0. Backup	6	### 0. Backup
4		7
5	It's useful to make a backup just in case things go south:	8	It's useful to make a backup just in case things go south:

doc/update/5.4-to-6.0.md

1	# From 5.4 to 6.0	1	# From 5.4 to 6.0
2		2
		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 or newer immediately.
		5	+
3	### Deprecations	6	### Deprecations
4		7
5	#### Global projects	8	#### Global projects

doc/update/6.0-to-6.1.md

1	# From 6.0 to 6.1	1	# From 6.0 to 6.1
2		2
		3	+## Warning
		4	+GitLab 6.1 is affected by critical security vulnerabilities CVE-2013-4490 and CVE-2013-4489. Please [update straight to 6.2](6.0-to-6.2.md).
		5	+
3	# In 6.1 we remove a lot of deprecated code.	6	# In 6.1 we remove a lot of deprecated code.
4	# You should update to 6.0 before installing 6.1 so all the necessary conversions are run.	7	# You should update to 6.0 before installing 6.1 so all the necessary conversions are run.
5		8

doc/update/6.1-to-6.2.md

1	# From 6.1 to 6.2	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	+
3	# You should update to 6.1 before installing 6.2 so all the necessary conversions are run.	6	# You should update to 6.1 before installing 6.2 so all the necessary conversions are run.
4		7
5	### 0. Backup	8	### 0. Backup