Releasing
OwnCloud Web can be hosted standalone for a dedicated oCIS backend or bundled as part of oCIS.
We follow the Semantic Versioning scheme. Therefore, each change is of one of the possible types: Bugfix, Change, Enhancement, Security
.
The highest type before a new release determines the version update number, so if it’s only Bugfix
and Security
changes the next release will be a PATCH
version bump, if there’s at least one Enhancement
within the changes this leads to a MINOR
version bump, while Change
type changes make for a new MAJOR
release version.
- Create a branch
release-$version
in https://github.com/owncloud/web. - Create a folder in
changelog
for the release version and datemkdir $major.$minor.$patchVersion_YYYY-MM-DD
. - Move all changelog items from the
changelog/unreleased/
folder to the$major.$minor.$patchVersion_YYYY-MM-DD
folder. - Run
./dev/scripts/bump_versions.sh $version
. This script will bump thepackage.json
files in all relevant packages. - Commit and push your changes.
- Run
./dev/scripts/create_and_push_tags.sh
. This script will create and push tags for the main app as well as all packages that need to be released. - After merging, wait for the CI to run on the merge commit.
- Go to the Releases section and click “Draft a new Release”.
- The release artifacts will be created automatically.
For oCIS the release assets need to be updated.