Provides RELEASE.md file with the release instructions. #15668
Conversation
Signed-off-by: Vitalii Parfonov <vparfono@redhat.com>
|
@vparfonov what about the bug-fix / service release process? are you going to provide this info in a separate PR ? |
Good catch, I will add here |
|
@vparfonov does che-parent / che-docs update suppose to be covered by this RELEASE.md? |
Signed-off-by: Vitalii Parfonov <vparfono@redhat.com>
che-bot
added
the
status/code-review
|
❌ E2E Happy path tests failed ❗ See Details
Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1) ℹ️ |
|
E2E tests of Eclipse Che Multiuser on OCP has failed:
|
|
OH NO! Happy path tests are failing for a new, document-only file. Why are the happy paths failing for a file that isn't part of the build? |
| * `git merge -X theirs {branchname}` | ||
| * `git push -f` | ||
| ##### 6. Close/release repository on Nexus | ||
| https://oss.sonatype.org/#stagingRepositories |
There was a problem hiding this comment.
Can this be scripted? Who has login/nexus credentials to make such a change?
| * on MacOS: `set_tag_version_images_macos.sh {tag}` | ||
| * `git commit` | ||
| * `git push` | ||
| ##### 4. Start pre-release testing. |
There was a problem hiding this comment.
Link to job? trigger instructions? Who to talk to? deadline for review? Criteria for rejection/approval?
There was a problem hiding this comment.
See https://github.com/eclipse/che-machine-exec/blob/master/RELEASE.md for example of how to link to the job(s) that run the builds/tests so we an immediate see status.
| 1 Update deploy_che.sh (should be deprecated soon - https://github.com/eclipse/che/issues/14069) default environment variables | ||
| 2 Update default version of plugins and editors in che.properties to released tag e.g `7.7.0` | ||
| 3 Update Helm charts with released tag e.g `7.7.0` | ||
|
|
There was a problem hiding this comment.
Could you list actual files that are changed or provide a link to PRs for 7.7.0 and 7.7.1?
| * Update dependencies: `sed -i -e "s#{version_old}#{next_version}#" pom.xml` | ||
| * `git commit` | ||
| * `git push --set-upstream origin set_next_version_in_master_{next_version}` | ||
| * Create PR |
There was a problem hiding this comment.
link to samples please. See https://github.com/eclipse/che-machine-exec/blob/master/RELEASE.md for examples of how to do this.
|
Is this RELEASE.md for all three Che projects (parent, docs, che) ? What about che-dev or che-lib? Will you also create RELEASE.md files for those repos? Or does the Che release process handle all 4 projects in one operation? |
There was a problem hiding this comment.
Unblocking so we can merge; remaining items to be done as enhancement as part of the doc generated from tomorrow's collab release with @mkuznyetsov and @vparfonov
che-bot
removed
the
status/code-review
Signed-off-by: Vitalii Parfonov vparfono@redhat.com
What does this PR do?
Provides RELEASE.md file with the release instructions.
What issues does this PR fix or reference?
Release Notes
Docs PR