Release Process for Envvars

Table of Contents

Special Scope Envvars
Extended Envvars
Ordinary Envvars
- Set the Correct IntroductionVersion
- Create Envvar Delta Files

For a new ocis release, some tasks are necessary to be done BEFORE releasing. Follow the steps carefully to avoid issues. Most of the docs related tasks are not part of the CI. With each step finished successfully, the next step can be started. Sometimes, due to last minute changes, steps need to be redone!

The following can be done at any time but it must be done latest when no envvar changes are made which is just before a new release gets finally tagged. The data generated must be part of the upcoming release and be merged before tagging/branching!

Special Scope Envvars

Ask the developers if envvars of this type have been changed (added or removed). See the Special Scope Envvars documentation for more details on how to manage such a change.

Extended Envvars

For more details see the Extended Envvars documentation.

Ordinary Envvars

Set the Correct IntroductionVersion

Once the release is cut, before creating the first release candidate, replace them with the actual semantic version (e.g. releaseX → 9.0.0). To find these placeholders in introductionVersion keys, you can run a helper script that originates in the documenation repository. To use this script, you must be in the linked directory, the ocis repository is located in parallel to the docs repository and the respective ocis branch is checked out and up-to-date.
```
./identify_envvar_placeholder_names.sh
```

A new production version MUST NOT contain any alphabetic identifyers but the semantic version only, using major, minor and a patch version, which is always 0!.

Create Envvar Delta Files

Envvar delta files are maintained via the ocis_helper go program in the root of the ownCloud documentation repository. The link directly opens the README.