From 543401f83b1a448ad55da128a26f40f70b1ae9d8 Mon Sep 17 00:00:00 2001 From: Kevin Breit Date: Tue, 20 Aug 2019 13:59:01 -0500 Subject: [PATCH] Collections documentatation - Add information about semantic versioning (#60969) --- docs/docsite/rst/dev_guide/collections_tech_preview.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/docsite/rst/dev_guide/collections_tech_preview.rst b/docs/docsite/rst/dev_guide/collections_tech_preview.rst index 58d18a301d8..dc1e82b4dd5 100644 --- a/docs/docsite/rst/dev_guide/collections_tech_preview.rst +++ b/docs/docsite/rst/dev_guide/collections_tech_preview.rst @@ -267,6 +267,12 @@ Once you upload a version of a collection, you cannot delete or modify that vers uploading. The only way to change a collection is to release a new version. The latest version of a collection (by highest version number) will be the version displayed everywhere in Galaxy; however, users will still be able to download older versions. +Collection versions use `Sematic Versioning ` for version numbers. Please read the official documentation for details and examples. In summary: + +* Increment major (for example: x in `x.y.z`) version number for an incompatible API change. +* Increment minor (for example: y in `x.y.z`) version number for new functionality in a backwards compatible manner. +* Increment patch (for example: z in `x.y.z`) version number for backwards compatible bug fixes. + Migrating Ansible content to a collection =========================================