Commit graph

6 commits

Author SHA1 Message Date
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
Takuya Noguchi
e4bd474126 Avoid installing Bundler 2.0 or higher
to always use Bundler 1.x on source install at this moment

Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
2019-01-22 16:27:55 +09:00
Fatih Sarhan
0902c44cc8 Update 10.5-to-10.6.md 2018-12-31 22:16:49 +00:00
Mattia Rizzolo
8426c04eeb
Recommend a --prune while git fetching
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>
2018-03-29 14:28:38 +02:00
Mike Greiling
43ceaf494f
update node and yarn dependencies within install/upgrade docs 2018-03-12 15:51:53 -05:00
James Lopez
6041d449b7
update guides for 10.6 2018-03-08 10:28:43 +01:00