Now MySQL is no longer supported, we need to change the docs

It's fine to upgrade from 11.11.x to 12.x, so we remove the requirement
to first upgrade to 12.0.x.

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

Jason Plum authored 6 years ago and Evan Read committed 6 years ago

Update the documented version requirement of Ruby inside of Upgrading
from Source to show GitLab 11.8 needs Ruby 2.5

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).

to always use Bundler 1.x on source install at this moment

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/52346

.

Signed-off-by: Rémy Coutable <remy@rymai.me>

This allows us (and others) to test drive Puma without it affecting all
users. Puma can be enabled by setting the environment variable
"EXPERIMENTAL_PUMA" to a non empty value.

Especially with the main gitlab repository, there tends to be tons of
stray branches, a continue `git fetch` without any -p will easily lead
to hundreds of "orphaned branches" in the local checkouts.

Signed-off-by: Mattia Rizzolo <mattia@mapreri.org>

Resolves #41438

Signed-off-by: Rémy Coutable <remy@rymai.me>

https://gitlab.com/gitlab-org/release-tools/blob/master/doc/release-candidates.md#creating-rc1