Updating release instructions

Author: gregorydlogan

README.md

@@ -56,31 +56,53 @@ If you aim to test against a remote server without using a proxy, you have the o
 NODE_ENV=development VITE_TEST_SERVER_URL="https://develop.opencast.org" VITE_TEST_SERVER_AUTH="admin:opencast" npm start
 ```
 
-How to cut a release for Opencast
----------------------------------
+
+How to cut a release for Opencast via the Github UI
+---------------------------------------------------
+
+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 [Create release tag](https://github.com/opencast/opencast-admin-interface/actions/workflows/create-release.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 [Process release](https://github.com/opencast/opencast-admin-interface/actions/workflows/process-release.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
+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
-   ```sh
-   DATE=$(date +%Y-%m-%d)
-   git tag -s -m "Release ${DATE}" "${DATE}"
-   git push upstream "${DATE}"
+   ```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 [Create release draft](https://github.com/opencast/opencast-admin-interface/actions/workflows/create-release.yml)
+4. Wait for the [Process release](https://github.com/opencast/opencast-admin-interface/actions/workflows/process-release.yml)
    workflow to finish
-    - It will create a new [GitHub release draft](https://github.com/opencast/opencast-admin-interface/releases)
-    - Review and publish the draft
-        - By selecting the previous release, Github can generate release notes automatically 
+    - 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. Submit a pull request against Opencast
-    - [Update the release](https://github.com/opencast/opencast/blob/542fc1f82181d1d4712ac8fc06c5ea9e16ae4033/modules/admin-ui-interface/pom.xml#L16-L17)
-    - Verify that the new release runs in Opencast, then create the pull request.
+5. Merge the upstream issue that the workflow above filed in [Opencast's main repository](https://github.com/opencast/opencast)
 
 
 Translating the Admin Interface