VMware Tanzu RabbitMQ for VMs docs

Branches in this Content Repo

The master branch is the tree-trunk, so ALWAYS make changes you want carried forward in this branch. This includes:

• Unreleased features
• Doc bug fixes
• Doc reorganization or enhancement

Then, if necessary, immediately cherry-pick/copy any changes that you want to push immediately to production into the appropriate branches listed below:

Book Repo

The book repo associated with this content repo is docs-book-rabbitmq.

Staging Environment

When a commit is made into any of the above branches, the documentation is deployed by this concourse build. All the supported versions will be accessible on the staging website.

Style Sheet

Use this section to specify spelling of special words for VMware Tanzu RabbitMQ for VMs:

• on-demand plan
• shared-VM plan
• dedicated-VM plan
• RabbitMQ Management UI

Making Your Documentation Changes Live

Click the deploy button in the pipeline! Living the dream :-D

Tag Management

We do not need to maintain older versions of the documentation so we're electing to not use tags to snapshot the state of the documentation for each previous patch version.

Contributing Documentation

If there's some documentation to add for an unreleased patch version of RabbitMQ then create a branch off of the live branch you intend to modify and create a Pull Request against that branch. Once the version that change is targeting is released, the Pull Request can be merged and will be live the next time a documentation deployment occurs.

If the documentation is meant to be target several released versions, then you'll need to create a Pull Request for each individual minor version.

Partials

Cross-product partials for VMware Tanzu RabbitMQ for VMs are single sourced from the PCF Docs Partials repo.

Previously, these partials were sourced from the v018.x branch of the On Demand Service Broker SDK content repo.

Releasing a New Minor Version

Since master is the latest and greatest documentation, the process would be to cut a x.x-live branch for the version that master was targeting during that time. A corresponding section in config.yml in the [docs-book-pcfservices][docs-book-pcfservices] repository would also need to be made.

After this point, master will then be the target for the next version of the RabbitMQ product tile.