Please report issues to Jira.
In order for documentation to be merged, the following are required:
Review from two members of the Maistra team
No broken links
No spelling errors
Documentation must be written according to the OpenShift documentation style guide.
Every Maistra minor release has a branch of the format
maistra-release in every repository. For example,
the 1.0 release has a branch
maistra-1.0 and 1.1 has a branch
maistra-1.1. This is
true for all branches including documentation. On every release, a tag is created for the current patch,
On every minor release, a new Maistra subdomain is created for the release in development, and the
Maistra website is switched to point at the current active release branch. The default branch for all
repositories is changed to point at the newest development branch. This means that the branch that
the Maistra.io website is based off of or that code is deployed from is always one minor release behind.
For example, when the default branch for Maistra.io is
maistra-1.2, then the branch that is being
deployed to Maistra.io is