This page is about publishing the documentation i.e. making changes or new releases visible to the public. For information on updating the source 'text' see the Getting Started Writing Documentation Guide
To try to avoid too much confusion we will refer to releases and branches when talking about the documentation source, and versions when talking about published documentation.
We will refer to the Read The Docs service as RTD.
To start with, you will need to create an account on Read The Docs (https://readthedocs.org/accounts/signup/) and then ask on the dev@ mailing list for someone to add you to the CloudStack Docs Projects.
The RTD uses the branches and tags to link versions of the documentation to moments in time in the source, to update the tags and branches seen by RTD, run a build of master
If the versions of documentation are linked to tags (ie release notes) then you need to:
The reading of tags is dynamic, so you can remove and re-add a tag and then rebuild that 'version'.
Merging a pull request will cause the version to be built and updated online automatically
When proofing a new version of documentation, you can set the version to 'protected' this stops the version from being browseable or from appearing to users in menus, but it is directly accessible.