update pipeline to only generate release notes

update release documentation

.pipelines/generate-release-notes-tagged.yml

@@ -1,23 +1,19 @@
-# Azure DevOps Pipeline building rp images and pushing to int acr
+# Azure DevOps Pipeline for generating release notes
 trigger: none
 pr: none
 
 variables:
-- template: vars.yml
 - name: TAG
-- group: PROD CI Credentials
 
 jobs:
-- job: Build_and_push_images
+- job: Generate_release_notes
   condition: startsWith(variables['build.sourceBranch'], 'refs/tags/v2')
-  displayName: Build release
+  displayName: Generate release notes
   pool:
     name: ARO-CI
-    demands: go-1.17
 
   steps:
   - template: ./templates/template-checkout.yml
-  - template: ./templates/template-az-cli-login.yml
     parameters:
       azureDevOpsJSONSPN: $(aro-v4-ci-devops-spn)
 
@@ -31,19 +27,6 @@ jobs:
       ## set the variable
       echo "##vso[task.setvariable variable=TAG]${TAG}"
 
-  - template: ./templates/template-push-images-to-acr-tagged.yml
-    parameters:
-      rpImageACR: $(RP_IMAGE_ACR)
-      imageTag: $(TAG)
-
-  - template: ./templates/template-az-cli-logout.yml
-  - script: |
-      cp -a --parents aro "$(Build.ArtifactStagingDirectory)"
-    displayName: Copy artifacts
-  - task: PublishBuildArtifacts@1
-    displayName: Publish Artifacts
-    name: aro_deployer
-
   - script: |
       set -xe
       MESSAGE="$(git for-each-ref refs/tags/${TAG} --format='%(contents)')"

docs/releases.md

@@ -23,15 +23,16 @@ you are tagging the right commit with the changes you want to release.
 
 ## Release pipeline
 
-Currently the release is done manually via the [pipeline](https://github.com/Azure/ARO-RP/blob/master/.pipelines/build-and-push-images-tagged.yml).
-The pipeline does not have any parameter, instead the pipeline is started on the `tag` as illustrated on the image.
-
-![Start pipelines with tag](img/pipelines.png "Aro Monitor Architecture")
+Currently the release is done manually via the [EV2 pipelines](https://msazure.visualstudio.com/AzureRedHatOpenShift/_wiki/wikis/ARO.wiki/233405/Performing-Release).
 
 
 ### Release page
 
-Once the release is built, new item is added to the [GitHub release page](https://github.com/Azure/ARO-RP/releases) with
+The generate release notes pipeline does not have any parameter, instead the pipeline is started on the `tag` as illustrated on the image.
+
+![Start pipelines with tag](img/pipelines.png "Aro Monitor Architecture")
+
+Once the release notes pipeline is finished, a new item is added to the [GitHub release page](https://github.com/Azure/ARO-RP/releases) with
 the following format:
 
 ```
@@ -44,11 +45,6 @@ ${{tag annotation}}
 - hash commit message
 - hash commit message
 
-## Assets:
-
-- aro binary
-- code zipped
-
 ```
 
 The title of the release is the used `git tag`. The description is extracted