fix paths to repos that have moved / default branches that have changed

Change-Id: Ie4182678855c6508b9cd7b981683d57b0f48d1fc
Signed-off-by: nickboldt <[email protected]>

README.md

@@ -22,18 +22,18 @@ Note that over time, this job, and all the jobs called by it, will be migrated t
 
 Currently all projects have automated release process, that consists of GitHub Actions workflow.
 Additionally, release logic is mostly contained within `make-release.sh` file, which allows to perform the release outside of GitHub Actions framework, should the need for it arises.
-For example, in the [Che server](https://github.com/eclipse/che) repo, GitHub action [release.yml](https://github.com/eclipse/che/actions/workflows/release.yml) runs the [make-release.sh](https://github.com/eclipse/che/blob/master/make-release.sh) release script.
+For example, in the [Che server](https://github.com/eclipse-che/che-server) repo, GitHub action [release.yml](https://github.com/eclipse-che/che-server/actions/workflows/release.yml) runs the [make-release.sh](https://github.com/eclipse-che/che-server/blob/main/make-release.sh) release script.
 
 GitHub Actions release workflows can be run by any user with write access to the repo in which the workflow is located. They use repository secrets, such as Quay or Docker.io credentials, that are required by most of the release workflows. If run outside GitHub, authorized users will need to provide their own secrets.
 
 ## Projects overview
-Most of the projects that are part of the weekly release cycle are also united in this project's workflow - the [Release - Orchestrate Overall Release Phases](https://github.com/eclipse/che-release/actions?query=workflow%3A%22Release+-+Orchestrate+Overall+Release+Phases%22), which runs the [make-release.sh](https://github.com/eclipse/che-release/blob/master/make-release.sh) release script.
+Most of the projects that are part of the weekly release cycle are also united in this project's workflow - the [Release - Orchestrate Overall Release Phases](https://github.com/eclipse-che/che-release/actions?query=workflow%3A%22Release+-+Orchestrate+Overall+Release+Phases%22), which runs the [make-release.sh](https://github.com/eclipse-che/che-release/blob/main/make-release.sh) release script.
 
 With the exception of some projects, it allows to perform the bulk of the release process with 1 click, running following projects in the correct order, making them complete a full release process - pushing commits or pull request to respective repositories, deploying artifacts etc. The projects that are covered by this workflow are:
 
-- [che](https://github.com/eclipse/che) - release artifact is the [eclipse/che-e2e](https://quay.io/repository/eclipse/che-e2e?tab=tags) container image
+- [che-e2e](https://github.com/eclipse/che) - release artifact is the [eclipse/che-e2e](https://quay.io/repository/eclipse/che-e2e?tab=tags) container image
 - [che-machine-exec](https://github.com/eclipse-che/che-machine-exec) - release artifact is the [eclipse/che-machine-exec](https://quay.io/repository/eclipse/che-machine-exec?tab=tags) container image
-- [che-theia](https://github.com/eclipse/che-theia) - release artifacts are several container images - [theia-dev](https://quay.io/repository/eclipse/che-theia-dev?tab=tags), [che-theia](https://quay.io/repository/eclipse/che-theia?tab=tags) and [che-theia-endpoint-runtime-binary](https://quay.io/repository/eclipse/che-theia-endpoint-runtime-binary?tab=tags)
+- [che-theia](https://github.com/eclipse-che/che-theia) - release artifacts are several container images - [theia-dev](https://quay.io/repository/eclipse/che-theia-dev?tab=tags), [che-theia](https://quay.io/repository/eclipse-che/che-theia?tab=tags) and [che-theia-endpoint-runtime-binary](https://quay.io/repository/eclipse/che-theia-endpoint-runtime-binary?tab=tags)
 - [che-devfile-registry](https://github.com/eclipse-che/che-devfile-registry) - release artifact is the [eclipse/che-devfile-registry](https://quay.io/repository/eclipse/che-devfile-registry?tab=tags) container image
 - [che-plugin-registry](https://github.com/eclipse-che/che-plugin-registry) - release artifact is the [eclipse/che-plugin-registry](https://quay.io/repository/eclipse/che-plugin-registry?tab=tags) container image
 - [che-dashboard](https://github.com/eclipse-che/che-dashboard) - release artifacts is the [eclipse/che-dashboard](https://quay.io/repository/eclipse/che-dashboard?tab=tags) container image
@@ -42,7 +42,7 @@ With the exception of some projects, it allows to perform the bulk of the releas
 - [kubernetes-image-puller](https://github.com/che-incubator/kubernetes-image-puller) - no actual release, only create a corresponding bugfix branch
 - [devworkspace-operator](https://github.com/devfile/devworkspace-operator) - release artifact is the [devfile/devworkspace-controller](https://quay.io/repository/devfile/devworkspace-controller?tab=tags) container image
 - [devworkspace-che-operator](https://github.com/che-incubator/devworkspace-che-operator) - release artifact is the [che-incubator/devworkspace-controller](https://quay.io/repository/devfile/devworkspace-controller?tab=tags) container image
-- [che](https://github.com/eclipse/che) - release artifacts are maven artifacts for Che server, as well as several container images:
+- [che server](https://github.com/eclipse-che/che-server) - release artifacts are maven artifacts for Che server, as well as several container images:
     [quay.io/eclipse/che-endpoint-watcher](https://quay.io/repository/eclipse/che-endpoint-watcher?tab=tags),
     [quay.io/eclipse/che-keycloak](https://quay.io/repository/eclipse/che-keycloak?tab=tags),
     [quay.io/eclipse/che-postgres](https://quay.io/repository/eclipse/che-postgres?tab=tags),
@@ -57,14 +57,14 @@ In the case of Che Operator, as well as workflows that depend on it - chectl, ch
 
 ## Release phases
 
-At the moment, [Release - Orchestrate Overall Release Phases]((https://github.com/eclipse/che-release/actions?query=workflow%3A%22Release+-+Orchestrate+Overall+Release+Phases%22)) job has the way of ordering the release by utilizing the concept of phases.
+At the moment, [Release - Orchestrate Overall Release Phases]((https://github.com/eclipse-che/che-release/actions?query=workflow%3A%22Release+-+Orchestrate+Overall+Release+Phases%22)) job has the way of ordering the release by utilizing the concept of phases.
 Currently there are several phases, representing an order of projects, which we can execute in parallel, as long as their dependent projects have been released. Projects in lower phases are those, on which projects from higher phase will depend.
 
-* Phase 1 - [che-devfile-registry](https://github.com/eclipse-che/che-devfile-registry), [che-machine-exec](https://github.com/eclipse-che/che-machine-exec), [che-jwt-proxy](https://github.com/eclipse/che-jwtproxy), [kubernetes-image-puller](https://github.com/che-incubator/kubernetes-image-puller), [devworkspace-operator](https://github.com/devfile/devworkspace-operator), [che-dashboard](https://github.com/eclipse-che/che-dashboard), [che](https://github.com/eclipse/che), [che-server](https://github.com/eclipse-che/che-server)
-* Phase 3 - [che-theia](https://github.com/eclipse/che-theia) - depends on [che-server](https://github.com/eclipse-che/che-server)
-* Phase 3 - [che-plugin-registry](https://github.com/eclipse-che/che-plugin-registry) - depends on [che-theia](https://github.com/eclipse/che-theia)
-* Phase 4 - [devworkspace-che-operator](https://github.com/che-incubator/devworkspace-che-operator) - depends on [devworkspace-operator](https://github.com/devfile/devworkspace-operator)
-* Phase 5 - [che-operator](https://github.com/eclipse-che/che-operator) - depends on phases 1 to 4
+* Phase 1 - [che-devfile-registry](https://github.com/eclipse-che/che-devfile-registry), [che-machine-exec](https://github.com/eclipse-che/che-machine-exec), [che-jwt-proxy](https://github.com/eclipse/che-jwtproxy), [kubernetes-image-puller](https://github.com/che-incubator/kubernetes-image-puller), [devworkspace-operator](https://github.com/devfile/devworkspace-operator), [che-dashboard](https://github.com/eclipse-che/che-dashboard), [che-e2e](https://github.com/eclipse/che), [che-server](https://github.com/eclipse-che/che-server)
+* Phase 3 - [che-theia](https://github.com/eclipse-che/che-theia) - depends on [che-server](https://github.com/eclipse-che/che-server)
+* Phase 4 - [che-plugin-registry](https://github.com/eclipse-che/che-plugin-registry) - depends on [che-theia](https://github.com/eclipse-che/che-theia)
+* Phase 5 - [devworkspace-che-operator](https://github.com/che-incubator/devworkspace-che-operator) - depends on [devworkspace-operator](https://github.com/devfile/devworkspace-operator)
+* Phase 6 - [che-operator](https://github.com/eclipse-che/che-operator) - depends on phases 1 to 4
 
 The phases list is a comma-separated list (default, which includes all phases "1,2,3,4,5"). Removing certain phases is useful, when you rerun the orchestration job, and certain projects shouldn't be released again. 
 Note that this approach will change, once a new system will be implemented, where we can more clearly specify dependencies between workflows, using special types of GitHub action.
@@ -73,7 +73,7 @@ Note that this approach will change, once a new system will be implemented, wher
 ## Release procedure
 1. [Create new release issue to report status and collect any blocking issues](https://github.com/eclipse/che/issues/new?assignees=&labels=kind%2Frelease&template=release.md&title=Release+Che+7.FIXME)
 
-2. To start a release, use the [Release - Orchestrate Overall Release Phases](https://github.com/eclipse/che-release/actions/workflows/release-orchestrate-overall.yml) workflow to trigger workflows in other Che repos. Workflows triggered align to the repos noted in the previous section. In the input, provide the version of Che, DevWorkspace controller, and phases to run. 
+2. To start a release, use the [Release - Orchestrate Overall Release Phases](https://github.com/eclipse-che/che-release/actions/workflows/release-orchestrate-overall.yml) workflow to trigger workflows in other Che repos. Workflows triggered align to the repos noted in the previous section. In the input, provide the version of Che, DevWorkspace controller, and phases to run. 
 
     2.1 If one of the workflows has crashed, inspect it. Apply fixes if needed, and restart it. You can restart individual workflow, or whole phase in orchestration job, whichever is simpler.
 
@@ -89,15 +89,11 @@ Note that this approach will change, once a new system will be implemented, wher
 
     3.3 Docs PR has to be merged by Docs team.
 
-4. When the release is complete, an e-mail should be sent to the `che-dev` mailing list. Additionally, a [Mattermost notification](https://github.com/eclipse/che-release/actions/workflows/release-send-mattermost-announcement.yml) can be sent to https://mattermost.eclipse.org/eclipse/channels/eclipse-che-releases
+4. When the release is complete, an e-mail should be sent to the `che-dev` mailing list. Additionally, a [Mattermost notification](https://github.com/eclipse-che/che-release/actions/workflows/release-send-mattermost-announcement.yml) can be sent to https://mattermost.eclipse.org/eclipse/channels/eclipse-che-releases
 
 --------------
 
 
 # Che release gotchas
 
-* VERSION file - should we add a test to verify we're not trying to re-release an existing release w/o an explicit override?
-* https://github.com/eclipse/che/issues/19334 - Mattermost notifications should clarify if the released artifact was successful or if the action failed. 
-* https://github.com/eclipse/che/issues/18879 - Implement proper tag recreation option for release scripts
 * https://github.com/eclipse/che/issues/17178 - Changelog generation contains too much information
-