Rename ocis-phoenix to ocis-web

2020-12-13 17:37:32 +01:00
parent 8ff6a8eac0
commit 25b51fc368
78 changed files with 319 additions and 326 deletions
@@ -0,0 +1 @@
+configuration.md
@@ -0,0 +1,10 @@
+---
+title: "ownCloud Web"
+date: 2018-05-02T00:00:00+00:00
+weight: 20
+geekdocRepo: https://github.com/owncloud/ocis
+geekdocEditPath: edit/master/docs/extensions/web
+geekdocFilePath: _index.md
+---
+
+This service embeds [ownCloud Web](https://github.com/owncloud/web) to provide a UI for ownCloud Infinite Scale.
@@ -0,0 +1,43 @@
+---
+title: "Releasing"
+weight: 40
+geekdocRepo: https://github.com/owncloud/ocis
+geekdocEditPath: edit/master/docs/extensions/web
+geekdocFilePath: releasing.md
+---
+
+{{< toc >}}
+
+## Releasing
+
+The next generation Web Frontend is shipped as an oCIS Extension. The `ocis-web` extension is also embedded in the single binary and part of the `ocis server` command.
+
+To update this package within all the deliveries, we need to update the package in the following chain from the bottom to the top.
+
+### Package Hierarchy
+
+- [ocis](https://githug.com/owncloud/ocis)
+    - [ocis-web](https://github.com/owncloud/ocis/tree/master/web)
+      - [ocis-pkg](https://github.com/owncloud/ocis/tree/master/ocis-pkg)
+      - [ownCloud Web](https://github.com/owncloud/web)
+
+#### Prerequisites
+
+Before updating the assets, make sure that [ownCloud Web](https://github.com/owncloud/web) has been released first
+and take note of its release tag name.
+
+#### Updating ocis-web
+
+1. Create a branch `release-$version`. in <https://github.com/owncloud/ocis>
+2. Create a Folder in `changelog` for the release version and date `mkdir $major.$minor.$patchVersion_YYYY-MM-DD`.
+3. Move all changelog items from the `changelog/unreleased/` folder to the `$major.$minor.$patchVersion_YYYY-MM-DD` folder.
+4. Update the go module `ocis-pkg` to the latest version <https://blog.golang.org/using-go-modules> .
+5. Update the ownCloud Web asset by adjusting the value of `WEB_ASSETS_VERSION` at the top of the Makefile and specify the tag name of the latest [ownCloud Web release](https://github.com/owncloud/web/tags).
+6. Run `make clean generate`.
+7. Create a changelog item for the update in the `changelog/$major.$minor.$patchVersion_YYYY-MM-DD` folder.
+8. Commit your changes.
+9. After merging, wait for the CI to run on the merge commit.
+10. Go to "Releases" in GH click "Draft a new Release".
+11. Use `v$major.$minor.$patch` as a tag (the `v` prefix is important) and publish it.
+12. The tag and the Release artifacts will be created automatically.
+