Page History

...

Updating Released Docs

Once an Ignite version is released, the release branch gets frozen and you won't be able to commit to it any changes (including documentation updates). This section explains how to update the docs in such conditions:a documentation update is merged to the master branch, cherry-pick it to the latest published version on the website or to a version that is to be released

1. Cherry-pick a commit from the master into 
2. Check if the ignite-{version}-docs branch has already been created after the version was released.
3. If the branch doesn't exist, create it from the ignite-{version} branch.
4. Commit the changes to the Ignite master.
5. Cherry-pick the changes to the If ignite-{version} -docs branch.Made the change visible is the latest version that is already published on the website, then republish the docs following this process: Updating Published Docs

...

Use the same command to generate an updated version of already released docs:

 ./build.sh --version=2.89.0 1 --github-branch=IGNITEignite-2.8-docs9.1

As for the rest, follow the procedure described in the Publishing New Version section above, except for step #5.

...