Commit Graph

20 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
Evan Read c2c2d04b3a Fix most instances of bare URLs in markdown 2019-01-24 06:52:33 +00:00
Achilleas Pipinellis 69b4c5c011 Exclude comments from specific docs 2017-11-01 15:56:40 +00:00
Achilleas Pipinellis e60ff02882 Fix broken links to docs
[ci skip]
2017-02-06 15:46:58 +01:00
Drew Blessing 2538c4ec8a Update docs based on customer upgrade from 4.0 [ci skip] 2016-06-22 16:27:00 -05:00
Ben Bodenmiller f73cb6ff74 note about latest details being on master branch
[ci skip]
2015-02-05 20:41:18 +01:00
Ewan Edwards ad6c372eee Fix a number of discovered typos, capitalization of developer and
product names, plus a couple of instances of bad Markdown markup.
2015-02-03 15:18:40 -08:00
Ben Bodenmiller 44185ace11 add prepare for upgrade section
helps detect and correct issues that may occur during upgrade before
they have already occurred. easier to address issues before you start
upgrade process.
2014-08-30 17:04:45 -07:00
Sytse Sijbrandij eea595971f Remove backticks in markdown links that cause ugly code blocks in GitLab. 2014-08-21 17:25:14 +02:00
Ben Bodenmiller 9e4a9935c2 Add dealing with newlines for editor to 5.1-to-6.0
backport of 2d681c0d1e
2014-08-04 15:22:15 -07:00
Ben Bodenmiller 73bdeff02e add command to start rails console 2014-08-04 00:57:32 -07:00
Robert Schilling 3aea2f6fe1 Fixes #171, correct links in update guide 5.1 to 6.0 2014-07-05 12:43:46 +02:00
Ciro Santilli fd348de76d Update docs to markdown style guide. 2014-06-03 23:16:31 +02:00
dosire 369bd858d8 We should only specify unsafe version, never give advise since it it perishable. 2014-03-24 15:17:43 +01:00
dosire 60e451fde4 Change canonical urls to GitLab Cloud. 2013-12-30 14:27:18 +01:00
Dmitriy Zaporozhets 7101b22c2e
Recommend gitlab-shell 1.7.9 in docs and check task
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2013-11-20 12:34:14 +02:00
Jacob Vosmaer 0ab0ca0d9d Use gitlab-shell 1.7.8 2013-11-14 13:35:45 +01:00
Jacob Vosmaer 81f69b5d31 Clarify upgrade steps 2013-11-02 17:24:43 +01:00
Jacob Vosmaer 88c15909f9 Add security warnings to update docs 2013-11-02 16:49:26 +01:00
Jacob Vosmaer d9cb02f1a2 Add a combined update doc from 5.1 to 6.0 2013-10-24 14:59:44 +02:00