delta/gitlab/gitlab-ce.git/doc/development/contributing, branch docs-avoid-CephFS-GlusterFS gitlab.com: gitlab-org/gitlab-ce.git Docs: Update contribution closing policy to include community attribution 2019-03-29T11:14:53+00:00 Lucas Charles me@lucascharles.me 2019-03-14T11:27:46+00:00 7f9ef2a585ffec746d0392f3edb2068bbb9c57b1 






Upgrade `gitlab-markup` to 1.7.0
2019-03-27T15:29:22+00:00

Gabriel Mazetto
brodock@gmail.com

2019-03-16T21:49:59+00:00

e5af7d83962934fc0463657a006acb54d4f85e85

The new version requires `python3` to be available. In omnibus
installation this is already a reality as we are currently pathing
previous `gitlab-markup` version to use `python3` instead of `python2`.

We are now requiring `python3` with the gem without having to patch it.

As a consequence to also make it easy to use it in development, we've
introduced a `Pipfile` and `Pipfile.lock`, working similarly to
`Gemfile` and `Gemfile.lock`, and added documentation on how to use
them.





The new version requires `python3` to be available. In omnibus
installation this is already a reality as we are currently pathing
previous `gitlab-markup` version to use `python3` instead of `python2`.

We are now requiring `python3` with the gem without having to patch it.

As a consequence to also make it easy to use it in development, we've
introduced a `Pipfile` and `Pipfile.lock`, working similarly to
`Gemfile` and `Gemfile.lock`, and added documentation on how to use
them.







Docs: Cleaning up the merge request workflow
2019-03-13T18:44:03+00:00

Marcel Amirault
ravlen@gmail.com

2019-03-13T18:44:03+00:00

cf89e3b2fe39f846e036652ba2c3ea32faf8d796












Docs: Fix broken anchors in development docs
2019-03-05T13:06:32+00:00

Marcel Amirault
ravlen@gmail.com

2019-03-05T13:06:32+00:00

9c8dc7ddf61eff16d56579a8818bb866ca3e3e5e












Fix misspellings in docs
2019-02-25T01:31:35+00:00

Takuya Noguchi
takninnovationresearch@gmail.com

2019-02-23T12:49:55+00:00

e8fee6b8f720b9b0340f40818a095fd941630423

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





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







Ensure all lists are surrounded by new lines
2019-02-22T13:17:10+00:00

Evan Read
eread@gitlab.com

2019-02-22T13:17:10+00:00

eb866309591f64a3cafb3c950b2cb6a0185595e8

Markdown renderers find it easier to determine
where lists start and end when lists are surrounded
by new lines.

For consistency, also ensure entries in the list
are aligned when they span multipls lines.





Markdown renderers find it easier to determine
where lists start and end when lists are surrounded
by new lines.

For consistency, also ensure entries in the list
are aligned when they span multipls lines.







Refactor the upgrading from source docs
2019-02-11T14:29:21+00:00

Yorick Peterse
yorickpeterse@gmail.com

2019-02-08T13:24:31+00:00

4d101979150e16c0cc8ac5e0380e9ef407542741

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





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







Merge branch 'gitlab-use-group-milestones' into 'master'
2019-02-07T17:12:37+00:00

Mike Lewis
mlewis@gitlab.com

2019-02-07T17:12:37+00:00

48647672837a9b13b2a4e3f048eb44a39968d12a

docs: GitLab uses group milestones to handle issues

See merge request gitlab-org/gitlab-ce!24953




docs: GitLab uses group milestones to handle issues

See merge request gitlab-org/gitlab-ce!24953






Merge branch 'docs/source-installation-requirements' into 'master'
2019-02-07T12:56:01+00:00

Marin Jankovski
marin@gitlab.com

2019-02-07T12:56:01+00:00

294129475c0977ce8bd32a6fa43b62af5022ee67

Update source installation to make it easier for release managers to work on releases

Closes gitlab-org/release/framework#113

See merge request gitlab-org/gitlab-ce!24967




Update source installation to make it easier for release managers to work on releases

Closes gitlab-org/release/framework#113

See merge request gitlab-org/gitlab-ce!24967






Add Go guidelines to developer docs
2019-02-06T16:10:12+00:00

Philippe Lafoucrière
plafoucriere@gitlab.com

2019-02-06T16:10:12+00:00

1effc189c3ceed1d21f0614d9724d37e7ca46e72