From bbd4ec13f1a2ceba493054fa6e846d749d9a875e Mon Sep 17 00:00:00 2001 From: Sandra McCann Date: Fri, 4 Sep 2020 15:37:44 -0400 Subject: [PATCH] clarify that collection names use same requirements as namespaces (#71639) --- docs/docsite/rst/dev_guide/developing_collections.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docsite/rst/dev_guide/developing_collections.rst b/docs/docsite/rst/dev_guide/developing_collections.rst index c812573a083..02f5a4823d8 100644 --- a/docs/docsite/rst/dev_guide/developing_collections.rst +++ b/docs/docsite/rst/dev_guide/developing_collections.rst @@ -268,7 +268,7 @@ To start a new collection: .. note:: - Both the namespace and collection names have strict requirements. See `Galaxy namespaces `_ on the Galaxy docsite for details. + Both the namespace and collection names use the same strict set of requirements. See `Galaxy namespaces `_ on the Galaxy docsite for those requirements. Once the skeleton exists, you can populate the directories with the content you want inside the collection. See `ansible-collections `_ GitHub Org to get a better idea of what you can place inside a collection. @@ -784,7 +784,7 @@ If your collection is part of Ansible, use one of the following three options t * Add a link to own changelogs or release notes in any format by opening an issue at https://github.com/ansible-community/ansible-build-data/ with the HTML link to that information. .. note:: - + For the first two options, Ansible pulls the changelog details from Galaxy so your changelogs must be included in the collection version on Galaxy that is included in the upcoming Ansible release. .. seealso::