GitLab supports utilizing a Cloud Object Storage service over[NFS](nfs.md) for holding
GitLab supports utilizing a Cloud Object Storage service rather than[NFS](nfs.md) for holding
numerous types of data. This is recommended in larger setups as object storage is
typically much more performant and reliable.
typically much more performant, reliable, and scalable.
For configuring GitLab to use Object Storage refer to the following guides:
1. Make sure the [`git` user home directory](https://docs.gitlab.com/omnibus/settings/configuration.html#moving-the-home-directory-for-a-user) is on local disk.
1. Configure [database lookup of SSH keys](../operations/fast_ssh_key_lookup.md)
to eliminate the need for a shared `authorized_keys` file.
1. Configure [object storage for backups](../../raketasks/backup_restore.md#uploading-backups-to-a-remote-cloud-storage).
1. Configure [object storage for job artifacts](../job_artifacts.md#using-object-storage)
including [incremental logging](../job_logs.md#new-incremental-logging-architecture).
1. Configure [object storage for LFS objects](../lfs/lfs_administration.md#storing-lfs-objects-in-remote-object-storage).
1. Configure [object storage for uploads](../uploads.md#using-object-storage-core-only).
1. Configure [object storage for merge request diffs](../merge_request_diffs.md#using-object-storage).
1. Configure [object storage for packages](../packages/index.md#using-object-storage)(optional feature).
1. Configure [object storage for dependency proxy](../packages/dependency_proxy.md#using-object-storage)(optional feature).
1. Configure [object storage for container registry](../packages/container_registry.md#container-registry-storage-driver)(optional feature).
1. Configure [object storage for Mattermost](https://docs.mattermost.com/administration/config-settings.html#file-storage)(optional feature).
1. Configure [object storage for packages](../packages/index.md#using-object-storage)(optional feature). **(PREMIUM ONLY)**
1. Configure [object storage for dependency proxy](../packages/dependency_proxy.md#using-object-storage)(optional feature). **(ULTIMATE ONLY)**
1. Configure [object storage for Pseudonymizer](../pseudonymizer.md#configuration)(optional feature). **(ULTIMATE ONLY)**
NOTE: **Note:**
One current feature of GitLab that still requires a shared directory (NFS) is
@@ -28,6 +28,18 @@ There are several ways to create a Release:
Start by giving a [description](#release-description) to the Release and
including its [assets](#release-assets), as follows.
## Release versioning
Release versions are manually assigned by the user in the Release title. GitLab uses [Semantic Versioning](https://semver.org/) for our releases, and we recommend you do too. Use `(Major).(Minor).(Patch)`, as detailed in the [GitLab Policy for Versioning](../../../policy/maintenance.md#versioning).
For example, for GitLab version `10.5.7`:
-`10` represents the major version. The major release was `10.0.0`, but often referred to as `10.0`.
-`5` represents the minor version. The minor release was `10.5.0`, but often referred to as `10.5`.
-`7` represents the patch number.
Any part of the version number can be multiple digits, for example, `13.10.11`.
### Release description
Every Release has a description. You can add any text you like, but we recommend