Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
11 tasks done
ibuziuk opened this issue Dec 17, 2019 · 17 comments
Closed
11 tasks done
Assignees
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Dec 17, 2019

Is your task related to a problem? Please describe.

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

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

@ibuziuk ibuziuk added kind/task Internal things, technical debt, and to-do tasks to be performed. area/doc Issues related to documentation labels Dec 17, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Dec 17, 2019
@ibuziuk ibuziuk changed the title Provide RELEASE.MD files with the release instructions to all the related repositories Provide RELEASE.md files with the release instructions to all the related repositories Dec 17, 2019
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. area/productization area/ci CI build and releases, PR testing, & whitelabel/productization issues and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. area/productization labels Dec 17, 2019
@ibuziuk ibuziuk added this to the 7.7.0 milestone Dec 18, 2019
@ibuziuk
Copy link
Member Author

ibuziuk commented Dec 19, 2019

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

@nickboldt
Copy link
Contributor

@davidfestal
Copy link
Contributor

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

@tolusha
Copy link
Contributor

tolusha commented Jan 15, 2020

@davidfestal
confirm

@tolusha
Copy link
Contributor

tolusha commented Jan 23, 2020

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

@gazarenkov
Copy link
Contributor

Who's working on che-plugin-registry?

@nickboldt
Copy link
Contributor

nickboldt commented Jan 28, 2020

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:

  • 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
Copy link
Member Author

ibuziuk commented Jan 28, 2020

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
Copy link
Contributor

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
Copy link
Member Author

ibuziuk commented Jan 29, 2020

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

@ibuziuk ibuziuk modified the milestones: 7.8.0, 7.9.0 Jan 29, 2020
@nickboldt
Copy link
Contributor

nickboldt commented Jan 29, 2020

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
Copy link
Member Author

ibuziuk commented Jan 29, 2020

Just for the record che-lib cease to exist

@nickboldt
Copy link
Contributor

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

@amisevsk
Copy link
Contributor

amisevsk commented Feb 3, 2020

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

@nickboldt
Copy link
Contributor

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
Copy link
Contributor

Resolving. Followup work in the 2 linked issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci CI build and releases, PR testing, & whitelabel/productization issues area/doc Issues related to documentation kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests