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

Release Che v7.3.2 #15107

Closed
22 of 23 tasks
l0rd opened this issue Nov 5, 2019 · 13 comments
Closed
22 of 23 tasks

Release Che v7.3.2 #15107

l0rd opened this issue Nov 5, 2019 · 13 comments
Assignees
Labels
kind/release Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.) kind/task Internal things, technical debt, and to-do tasks to be performed.
Milestone

Comments

@l0rd
Copy link
Contributor

l0rd commented Nov 5, 2019

Is your task related to a problem? Please describe.

We may need to release Che 7.3.2. This task is to track the list of fixes that should be added to the release:

Release status

@l0rd l0rd added kind/task Internal things, technical debt, and to-do tasks to be performed. team/productization labels Nov 5, 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 Nov 5, 2019
@l0rd l0rd removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 5, 2019
@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Nov 5, 2019

Could you, please, say if it affects CRW 2.0.0?

@l0rd
Copy link
Contributor Author

l0rd commented Nov 5, 2019

Yes this is a list of eventual fixes needed for CRW 2.0.0

@dmytro-ndp
Copy link
Contributor

Thanks.

@ibuziuk
Copy link
Member

ibuziuk commented Nov 6, 2019

@l0rd I think we should also include #15006

@vparfonov
Copy link
Contributor

what due dates?

@l0rd
Copy link
Contributor Author

l0rd commented Nov 6, 2019

@ibuziuk added

@vparfonov we want this to be included in CRW 2.0.0 so we should release at the beginning of next week. Something important to mention is that as far as I am concerned those are not blockers: if we don't have a fix for them by the beginning of next week we can add them in the doc among "Known Issues". In other words: let's do the 7.3.2 release at latest next Tuesday with whatever we have. Does that make sense?

@ibuziuk
Copy link
Member

ibuziuk commented Nov 6, 2019

@amisevsk I think we probably need to backport tthose PRs to 7.3.2

@amisevsk
Copy link
Contributor

Cherry-pick PRs for registries: eclipse-che/che-plugin-registry#294, eclipse-che/che-devfile-registry#143

@evidolob
Copy link
Contributor

We need #15194 for 7.3.2

@ibuziuk
Copy link
Member

ibuziuk commented Nov 14, 2019

@evidolob @l0rd Plugin installation fails from che-theia workspace · Issue #15006 · is closed but was it cherry-picked on 7.3.x ?

@l0rd
Copy link
Contributor Author

l0rd commented Nov 14, 2019

@ibuziuk the fix required a commit on eclipse/che side #15180. Not sure you tested with that commit as well.

@ibuziuk
Copy link
Member

ibuziuk commented Nov 14, 2019

Dashboard restart is cherry-picked - #15194
Just want to make sure that all critical fixes are also backported to 7.3.x

@ibuziuk
Copy link
Member

ibuziuk commented Nov 20, 2019

The release has been done. Closing

@ibuziuk ibuziuk closed this as completed Nov 20, 2019
@sunix sunix added the kind/release Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.) label Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/release Issue dedicated to a release (content, status, related PR, go/nogo/problem discussion, etc.) kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

10 participants