Provide RELEASE.md files with the release instructions to all the related repositories

[ibuziuk]

Is your task related to a problem? Please describe.

List of components / repositories where the RELEASE.md files should be created:

• che-theia https://github.com/eclipse/che-theia/blob/master/RELEASE.md
• che-machine-exec - che #15506 Adding RELEASE.md file with instructions for Major/Minor and Service/Bugfix releases che-machine-exec#68 + new RELEASE.sh script automates all the... che-machine-exec#71 (make-release.sh script)
• che-plugin-registry rename RELEASE.MD -> RELEASE.md; clean up... che-plugin-registry#361 (make-release.sh script)
• che-devfile-registry - che #15506 Adding RELEASE.md file with instructions for Major / Minor and Service / Bugfix releases che-devfile-registry#176 + provide script for doing devfile reg... che-devfile-registry#180 (RELEASE.sh script)
• che Provides RELEASE.md file with the release instructions. #15668 PR merged but followup work required to provide more details in order to make this vague process scriptable
  • che-parent
  • che-docs
  • che
• che-operator Add RELEASE.md che-operator#152
• chectl - chore(release): update release script and add RELEASE.md che-incubator/chectl#443
• che-plugin-broker Add RELEASE.md and release automation script che-plugin-broker#90

The RELEASE.md should contain a clear set of instructions required for both general and bugfix releases.

[ibuziuk]

PR for for che-machine-exec - eclipse-che/che-machine-exec#68

[nickboldt]

To better track work in progress i've started this sheet:

https://docs.google.com/spreadsheets/d/1CnFjcwJeNgAahMv4EQq6-uGHpU09EeheeZO7kt4UMtg/edit?folder=0ALk9kk_xmhjNUk9PVA#gid=0

[davidfestal]

@tolusha do you confirm you're finally planning to work on the operator side of this ?

[tolusha]

@davidfestal
confirm

[tolusha]

PR for che-operator
eclipse-che/che-operator#152

[gazarenkov]

Who's working on che-plugin-registry?

[nickboldt]

I believe that one is owned by @ibuziuk but ... afaict it's basically the same as the README/script for che-machine-exec or devfile registry, except with one additional step: generating the latest 2 plugins meta.yaml for che-machine-exec and che-theia.

So for $VERSION = 7.8.0 I could be talked into taking that one over and scripting it:

• copy https://raw.githubusercontent.com/eclipse/che-plugin-registry/master/v3/plugins/eclipse/che-machine-exec-plugin/nightly/meta.yaml into new folder $VERSION/; sed replace three lines:

• firstPublicationDate moves to today
• version: nightly becomes version: $VERSION
• image: ...:nightly becomes image: ...:$VERSION

• Then repeat for che-theia, but using :next instead of :nightly because for some reason they're not using the same euphemism for 'latest'.

Also change this:

title: Eclipse Theia development version.
description: Eclipse Theia, get the latest release each day.

to this:

title: Eclipse Theia for Eclipse Che ...  (why do we need "for Eclipse Che" here?)
description: Eclipse Theia

• Then tag/branch as for che-devfile-registry & che-machine-exec releases.

[ibuziuk]

PR for plugin-registry has been sent - eclipse-che/che-plugin-registry#360
@vparfonov could you please finalize the docs for parent, docs, che and I believe we will be able to close the issue after that 🤞

[nickboldt]

PR for plugin reg merged. Followup (copy tweaks and new make-release.sh script):

eclipse-che/che-plugin-registry#361

Similar tweaks for consistency in devfile reg:

eclipse-che/che-devfile-registry#187

[ibuziuk]

@nickboldt is there anything else expected from Hosted Che team regarding the release instructions or can we close the issue ?

[nickboldt]

Waiting on content from @vparfonov and @mkuznyetsov -- the release.md for che is incomplete and we're missing equivalent instructions for che-dev, che-lib, che-parent, che-docs.

But I've removed the hosted-che label and assignees who are no longer involved.

[ibuziuk]

Just for the record che-lib cease to exist

[nickboldt]

Yes, we only need che-parent, che-doc, and che pushed to maven central now. Hooray for simplified releases. (Meanwhile, >20 sidecar images...) :|

[amisevsk]

PR for che-plugin-broker merged: eclipse-che/che-plugin-broker#90

[nickboldt]

Instructions exist for che-parent, docs and che, but they're in dire need of more details.

https://github.com/eclipse/che-parent/blob/master/RELEASE.md#4-closerelease-staging-repository-on-nexus

• who has permission?
• what is required to be done?
• can we automate this like we did for JBoss Tools releases to JBoss Nexus ?

https://github.com/eclipse/che-parent/blob/master/RELEASE.md#1-create-branch-for-release-preparation-and-next-bugfixes

• don't you create a tag in the branch as well?

Same questions for docs and che.

^^ @vparfonov @mkuznyetsov ^^

[nickboldt]

Resolving. Followup work in the 2 linked issues.