Add how to release documentation

docs/update_repo.md

@@ -7,7 +7,7 @@ The basic update is to merge in upstream changes from a target release version a
 git checkout -b update-to-<target tag>
 git remote add upstream https://github.com/theforeman/foreman-operations-collection
 git fetch upstream
-git merge upstream/<target tag>
+git merge <target tag>
 make branding
 ```
 
@@ -20,3 +20,18 @@ When new roles are added from upstream there are two options for dealing with th
  1. A new role that isn't being shipped with Satellite. This role should be added to the Makefile removal list and then re-run `make branding`.
  2. A new role that is being shipped with Satellite. This role should have a test folder `roles/<new role>/molecule/satellite` added to it.
     This test folder should include any testing needed to verify this role in a Satellite context.
+
+# How to Release Repository
+
+After making local changes for branding:
+
+   * Create a pull request with the changes
+
+   * After merging, tag the merge commit with `<version number>` (i.e. v1.2.0).
+     Please use signed tags.
+
+   * Generate a copy of the source tarball locally: `make dist`
+
+   * Visit the UI for the tag (e.g. [v1.2.0](https://github.com/RedHatSatellite/satellite-operations-collection/releases/tag/v1.2.0) and click the "Create release from tag" button
+
+   * Edit the release title to the name of the tag (e.g. v1.2.0) and upload the generated source tarball, then click `Publish Release`