|
| 1 | += Documentation for Hazelcast Platform Operator |
| 2 | +// Settings: |
| 3 | +ifdef::env-github[] |
| 4 | +:warning-caption: :warning: |
| 5 | +endif::[] |
| 6 | +// URLs: |
| 7 | +:url-org: https://github.com/hazelcast |
| 8 | +:url-contribute: https://github.com/hazelcast/hazelcast-docs/blob/develop/.github/CONTRIBUTING.adoc |
| 9 | +:url-ui: {url-org}/hazelcast-docs-ui |
| 10 | +:url-playbook: {url-org}/hazelcast-docs |
| 11 | +:url-staging: https://hardcore-allen-f5257d.netlify.app/ |
| 12 | +:url-cc: https://creativecommons.org/licenses/by-nc-sa/3.0/ |
| 13 | +:url-operator-docs: {url-org}/hazelcast-platform-operator-docs |
| 14 | +:url-mc-docs: {url-org}/management-center-docs |
| 15 | + |
| 16 | +image:https://img.shields.io/badge/Build-Staging-yellow[link="{url-staging}"] |
| 17 | + |
| 18 | +This repository contains the Antora components for the Hazelcast Platform Operator documentation. |
| 19 | + |
| 20 | +The documentation source files are marked up with AsciiDoc. |
| 21 | + |
| 22 | +== Docs Structure |
| 23 | + |
| 24 | +This section describes some important information about how this repository is structured: |
| 25 | + |
| 26 | +- The component name, version, and start page are configured in each branch's `antora.yml` file. |
| 27 | +- The navigation for all modules is stored in the ROOT module's `nav.adoc` file. |
| 28 | +- The {url-playbook}[docs site playbook] instructs Antora to automatically build the site using content in the `main` branch as well as any branches that are prefixed with `v/`. |
| 29 | + |
| 30 | +== Release Workflow |
| 31 | + |
| 32 | +Documentation for new releases is hosted in versioned branches that are prefixed with `v/`. The `latest-dev` content (snapshot content) is stored in the `main` branch. |
| 33 | + |
| 34 | +We support documentation for the latest patch releases of minor versions. For example, content for the `5.0` version is hosted in the `v/5.0` branch. This branch contains content for the latest patch release of version 5.0. |
| 35 | + |
| 36 | +NOTE: The documentation build process is triggered whenever you create a new branch with the `v/` prefix, push to an existing `v/` branch, or push to the `main` branch. |
| 37 | + |
| 38 | +=== Snapshot Releases |
| 39 | + |
| 40 | +Add the new snapshot version to the following: |
| 41 | + |
| 42 | +[cols="1m,1m,1m,1m"] |
| 43 | +|=== |
| 44 | +|Repository|Branch|File|Fields |
| 45 | + |
| 46 | +|{url-operator-docs}[hazelcast-platform-operator-docs] |
| 47 | +|main |
| 48 | +|docs/antora.yml |
| 49 | +a| |
| 50 | +- `version` |
| 51 | +- `display_version` |
| 52 | +- `full-version` |
| 53 | + |
| 54 | +|{url-playbook}[hazelcast-docs] |
| 55 | +a|`main` and `develop` |
| 56 | +|_redirects |
| 57 | +|/hazelcast-operator/latest-dev/* |
| 58 | + |
| 59 | +| |
| 60 | +| |
| 61 | +|search-config.json |
| 62 | +a|Update the snapshot version in these fields: |
| 63 | + |
| 64 | +- `start_urls.tags` |
| 65 | +- `start_urls.variables.version` |
| 66 | + |
| 67 | +|=== |
| 68 | + |
| 69 | +=== Latest Releases |
| 70 | + |
| 71 | +Add the `major.minor` version to the following: |
| 72 | + |
| 73 | +[cols="1m,1m,1m,1m"] |
| 74 | +|=== |
| 75 | +|Repository|Branch|File|Fields |
| 76 | + |
| 77 | +|{url-operator-docs}[hazelcast-platform-operator-docs] |
| 78 | +|v/{major.minor version} |
| 79 | +|docs/antora.yml |
| 80 | +a| |
| 81 | +- `version` |
| 82 | +- `display_version` |
| 83 | + |
| 84 | +|{url-playbook}[hazelcast-docs] |
| 85 | +a|`main` and `develop` |
| 86 | +|_redirects |
| 87 | +|/hazelcast-operator/latest/* |
| 88 | + |
| 89 | +| |
| 90 | +| |
| 91 | +|search-config.json |
| 92 | +a| Create a new object in the `start_urls` array. |
| 93 | + |
| 94 | +`` |
| 95 | +{ |
| 96 | + "url": "https://docs.hazelcast.com/hazelcast-operator/(?P<version>.*?)/", |
| 97 | + "tags": [ |
| 98 | + "hazelcast-operator-{major.minor version}" |
| 99 | + ], |
| 100 | + "variables": { |
| 101 | + "version": ["{major.minor version}"] |
| 102 | + }, |
| 103 | + "selectors_key": "operator" |
| 104 | +} |
| 105 | +`` |
| 106 | + |
| 107 | +|=== |
| 108 | + |
| 109 | +Add the full version `major.minor.patch` to the following: |
| 110 | + |
| 111 | +[cols="1m,1m,1m"] |
| 112 | +|=== |
| 113 | +|Repository|File|Fields |
| 114 | + |
| 115 | +|{url-operator-docs}[hazelcast-platform-operator-docs] |
| 116 | +|docs/antora.yml |
| 117 | +a| |
| 118 | +- `full-version` |
| 119 | +|=== |
| 120 | + |
| 121 | +=== Patch Releases |
| 122 | + |
| 123 | +In the `v/` branch for the minor version whose patch you are releasing, update the `asciidoc.attributes.full-version` field in the `antora.yml` file to the new patch version. For example, if you are releasing version 5.0.3, find the `v/5.0` branch and update the `asciidoc.attributes.full-version` field in the `antora.yml` file with 5.0.3. |
| 124 | + |
| 125 | +NOTE: As soon as you push content to this branch, GitHub will trigger a new build of the site, which will include your new content. |
| 126 | + |
| 127 | +=== Creating Release Branches |
| 128 | + |
| 129 | +. If you are releasing a new major version, create a release branch from the `main` branch. |
| 130 | ++ |
| 131 | +For example, if you are releasing version 5.1, create a new release branch named `5.1` from the `main` branch. |
| 132 | + |
| 133 | +. Update the fields mentioned in <<latest-releases, Latest Releases>>. |
| 134 | + |
| 135 | +. Remove the `prerelease: true` field from the `docs/antora.yml` file of the `hz-docs` repository. |
| 136 | ++ |
| 137 | +IMPORTANT: If you are creating a branch for a beta release, do not remove this field. |
| 138 | + |
| 139 | +. When you are ready to release, create a maintentance branch from the release branch. |
| 140 | ++ |
| 141 | +NOTE: As soon as you push the maintenance branch to the repository, GitHub will trigger a new build of the site, which will include your new content. |
| 142 | + |
| 143 | +. Make sure to delete the release branch. |
| 144 | ++ |
| 145 | +For example, if you released version `5.1`, delete the `5.1` branch. This step helps to keep the repository clean of release branches. |
| 146 | + |
| 147 | +== GitHub Actions |
| 148 | + |
| 149 | +To automate some elements of the build process, this repository includes the following GitHub Actions: |
| 150 | + |
| 151 | +.GitHub Actions |
| 152 | +[cols="m,a,a"] |
| 153 | +|=== |
| 154 | +|File |Description |Triggers |
| 155 | + |
| 156 | +|validate-site.yml |
| 157 | +|Validates that all internal and external links are working |
| 158 | +|On a pull request to the `main` branch and `v/` maintenance branches |
| 159 | + |
| 160 | +|build-site.yml |
| 161 | +|Builds the production documentation site by sending a build hook to Netlify (the hosting platform that we use) |
| 162 | +|On a push to the `main` branch and any `v/` maintenance branches |
| 163 | +|=== |
| 164 | + |
| 165 | +== Contributing |
| 166 | + |
| 167 | +If you want to add a change or contribute new content, see our {url-contribute}[contributing guide]. |
| 168 | + |
| 169 | +To let us know about something that you'd like us to change, consider {url-org}/hazelcast-operator/issues/new[creating an issue]. |
| 170 | + |
| 171 | +== License |
| 172 | + |
| 173 | +All documentation is available under the terms of a link:{url-cc}[Creative Commons License] |
0 commit comments