gitlab-org--gitlab-foss/doc/development/contributing
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
..
community_roles.md Improve the contributing documentation 2018-10-11 16:33:46 +02:00
design.md Improve the contributing documentation 2018-10-11 16:33:46 +02:00
index.md Make unordered lists conform to styleguide 2019-01-08 12:21:09 +10:00
issue_workflow.md GitLab uses group milestones to handle issues 2019-02-06 16:51:00 +09:00
merge_request_workflow.md Refactor the upgrading from source docs 2019-02-11 15:29:21 +01:00
style_guides.md Add Go guidelines to developer docs 2019-02-06 16:10:12 +00:00