Commit graph

11 commits

Author SHA1 Message Date
Marcel Amirault
0d4c6a14d8 Update redirected links to final destinations
This updates redirected links in integration, update, user
and workflow dirs. Should now link to final URLs to avoid
redirect hops
2019-07-08 23:14:29 +00:00
Nick Thomas
8802dd24ec
Update the docs to reflect lack of MySQL support
Now MySQL is no longer supported, we need to change the docs
2019-06-19 14:11:01 +01:00
Yorick Peterse
91510305e6
Correct upgrade guides for 12.0
It's fine to upgrade from 11.11.x to 12.x, so we remove the requirement
to first upgrade to 12.0.x.
2019-06-19 13:36:38 +02:00
Yorick Peterse
e2aaa602e8
Added source upgrade guides for 12.0.0 2019-06-18 15:32:48 +02:00
Jacob Vosmaer
37e995f7dc Use Go 1.11.10 in source installations 2019-06-11 15:23:49 +00:00
Æx
af10b5291c Add git 2.21 install from update_source 2019-06-07 07:09:49 +00:00
Richard Hancock
3a277320fb Rjh/doc fixes for source install 2019-05-15 16:30:30 +00:00
Stan Hu
a50951d73a Upgrade Ruby version to 2.6.3
Ruby 2.6 offers better performance and memory usage:
https://www.rubyguides.com/2018/11/ruby-2-6-new-features/

Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/57323
2019-05-08 06:21:14 -07:00
Marcel Amirault
5f7b4a7b00 Docs: Merge EE doc/​update to CE 2019-05-05 12:17:20 +00:00
Jason Plum
599dfc9543 Update upgrading_from_source.md for Ruby 2.5
Update the documented version requirement of Ruby inside of Upgrading
from Source to show GitLab 11.8 needs Ruby 2.5
2019-03-07 04:00:52 +00:00
Yorick Peterse
4d10197915
Refactor the upgrading from source docs
Instead of requiring one separate document for every version (which is
created by release managers), we now use a single document for both
Community Edition and Enterprise Edition. This allows developers to add
guidelines right away, instead of release managers having to determine
what to add.

Version specific upgrading instructions are placed in a separate
section. This prevents instructions from lingering around for many
versions should a developer forget to remove them. This also ensures
that all instructions are kept in a single place, instead of being
spread across different documents.

A minor downside is that CE and EE guidelines now live in the same
document, which could cause merge conflicts. Since we are working
towards a single codebase, this should only be an issue until we merge
the codebases together; something we expect to do in the coming months.

This commit also removes all old upgrading instructions, but these can
still be accessed using Git branch specific URLs (included in the
updating README).
2019-02-11 15:29:21 +01:00