chore(docs): updates release.md (#272)

* feat: updates to release.md

* Update RELEASE.md

Co-authored-by: Stefano Charissis <[email protected]>

---------

Co-authored-by: Stefano Charissis <[email protected]>

Author: jelias2

RELEASE.md

@@ -1,34 +1,27 @@
 # Release Process
 
-This document outlines the steps and processes for releasing a new version of one or more services in the `ethereum-optimism/infra` repository. The release process is driven by a GitHub Action (`Tag Service`) and subsequently triggers workflows in CircleCI to build and publish updated [these services/components](https://github.com/ethereum-optimism/infra/blob/main/ops/tag-service/tag-tool.py#L6-L13) selectively.
+This documents the process of releasing a new version of one or more services in the `ethereum-optimism/infra` repository.
+The release process is driven by CircleCI to build and publish components
 
 ## Release Process Overview
 
-1. **Tagging and Releasing with GitHub Action**
+1. **Tagging and Releasing**
 
-   The release process is initiated by the "Tag Service" GitHub Action [here](https://github.com/ethereum-optimism/infra/actions/workflows/tag-service.yml). To trigger this action:
-   
-   - Select the branch containing the action—usually `main`.
-   - Choose the appropriate parameters to specify which services should be tagged and released.
+   The release process is initiated by creating a new tag on the main branch
+   The tag should be prefixed with the component and suffixed with release semver
+   Ex. op-acceptor/v0.1.6 / <component>/v<major>.<minor>.<patch>
 
    > **Note**: Generally, the branch used for releases is `main` but if needed, you can use a different branch, say, if you'd like to create test releases from your branch.
 
-   The GitHub Action relies on `ops/tag-service`, which manages key release functions:
-   
-   - Identifying supported services.
-   - Determining version increments.
-   - Specifying precise tags for release.
-   - Configuring the release title and release notes.
-
 2. **Triggering the CircleCI Workflow**
 
-   Once a release tag is created by the above Github Action, the CircleCI `release` workflow is triggered. The configuration for this workflow is located in `.circle/config.yml` within the tagged release.
+   Once a release tag is created, the CircleCI `release` workflow is triggered. The configuration for this workflow is located in `.circle/config.yml` within the tagged release.
 
    The workflow compares differences between the newly released tag and the `main` branch (the base revision). Based on these differences, it selectively toggles parameters to `true` only for services that have been updated. This prevents unnecessary builds or deployments when minor changes are made to unrelated services. [Refer to config here](https://github.com/ethereum-optimism/infra/blob/main/.circleci/config.yml#L18-L25).
 
 3. **Approval Process for Certain Tags**
 
-   For specific tags ([listed here](https://github.com/ethereum-optimism/infra/blob/main/.circleci/continue_config.yml#L533)), the workflow pauses with a hold step that requires approval from a member of the `@release-managers` team on `ethereum-optimism` GitHub Organisation. Once approved, the workflow continues.
+   For specific tags ([listed here](https://github.com/ethereum-optimism/infra/blob/main/.circleci/continue_config.yml#L590)), the workflow pauses with a hold step that requires approval from a member of the `@release-managers` team on `ethereum-optimism` GitHub Organisation. Once approved, the workflow continues.
 
 4. **Selective Component Release**
 
@@ -38,4 +31,12 @@ This document outlines the steps and processes for releasing a new version of on
    - `docker-publish`: Publishes that image.
    - `docker-tag-op-stack-release`: Attaches from more tags to that image compliant with OP-Stack releases.
 
-   Only the components that were updated in the GitHub release are built and delivered as Docker images.
+   Only the components that were updated in the circle ci release are built and delivered as Docker images.
+
+## Requesting a Release as External Contributor
+
+Typically a reviewer will publish a new release after reviewing the contribution.
+Feel free to request a new release as part of the creating the PR in the PR description.
+
+If no release has been created feel free to create an issue or reach out in the OP Stack Protocol R&D Discord
+