Documenting releases, or lack thereof

Author: gregorydlogan

README.md

@@ -57,52 +57,11 @@ NODE_ENV=development VITE_TEST_SERVER_URL="https://develop.opencast.org" VITE_TE
 ```
 
 
-How to cut a release for Opencast via the Github UI
----------------------------------------------------
+Admin releases
+--------------
 
-1. (Optional) Run the GitHub Actions workflow [Crowdin » Download translations
-   ](https://github.com/opencast/opencast-admin-interface/actions/workflows/crowdin-download-translations.yml)
-   to ensure all changes from Crowdin are included in the new release.
-
-2. Use the [Release » Create release tag](https://github.com/opencast/opencast-admin-interface/actions/workflows/release-cut-tag.yml)
-   workflow to create a correctly named tag in the appropriate branch.  When running the workflow via the dropdown
-   ensure you select the correct branch for the release!
-
-3. Wait for the [Release » Process release tag](https://github.com/opencast/opencast-admin-interface/actions/workflows/release-build.yml)
-   workflow to finish
-    - It will create a new [GitHub release](https://github.com/opencast/opencast-admin-interface/releases)
-      - Review the release and make sure the notes are right, update them if not.
-        - By selecting the previous release, Github can generate release notes automatically
-      - This review isn't required to happen prior to the next step!
-
-5. Merge the upstream issue that the workflow above filed in [Opencast's main repository](https://github.com/opencast/opencast)
-
-
-How to cut a release for Opencast manually with git
----------------------------------------------------
-
-1. (Optional) Run the GitHub Actions workflow [Crowdin » Download translations
-   ](https://github.com/opencast/opencast-admin-interface/actions/workflows/crowdin-download-translations.yml)
-   to ensure all changes from Crowdin are included in the new release.
-
-2. Switch to the commit you want to turn into the release - make sure this is the on `develop` or an `r/N.x` branch
-
-3. Create and push a new tag
-   ```bash
-    BRANCH=N.x (make sure the version you write here matches the branch you have checked out)
-    DATE=$(date +%Y-%m-%d)
-    git tag -sm "Release $BRANCH-$DATE" -s "$BRANCH-$DATE"
-    git push upstream "$BRANCH-$DATE":"$BRANCH-$DATE"
-   ```
-
-4. Wait for the [Release » Process release tag](https://github.com/opencast/opencast-admin-interface/actions/workflows/release-build.yml)
-   workflow to finish
-    - It will create a new [GitHub release](https://github.com/opencast/opencast-admin-interface/releases)
-      - Review the release and make sure the notes are right, update them if not.
-        - By selecting the previous release, Github can generate release notes automatically
-      - This review isn't required to happen prior to the next step!
-
-5. Merge the upstream issue that the workflow above filed in [Opencast's main repository](https://github.com/opencast/opencast)
+The admin module no longer cuts releases itself.  Opencast's release manager will create tags as appropriate and push
+as part of the release process.
 
 
 Translating the Admin Interface