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

Add 7.3.2 and 7.3.3 versions of che-theia/che-machine-exec #319

Merged
merged 1 commit into from
Dec 10, 2019

Conversation

amisevsk
Copy link
Contributor

@amisevsk amisevsk commented Dec 10, 2019

What does this PR do?

Add the 7.3.2 and 7.3.3 bugfix version of che-machine-exec and che-theia to master branch to ensure compatibility when updating Che.

Metas are copied from 7.3.3 tag.

Fixes eclipse-che/che#15444 for future releases.

Add the 7.3.2 and 7.3.3 bugfix version of che-machine-exec and che-theia
to master branch to ensure compatibility when updating Che.

Signed-off-by: Angel Misevski <amisevsk@redhat.com>
@ibuziuk ibuziuk mentioned this pull request Dec 10, 2019
21 tasks
Copy link
Contributor

@nickboldt nickboldt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should these old versions be marked deprecated/auto-update to the latest? Compatibility is good but so is staying current w/ 7.x.next

@nickboldt
Copy link
Contributor

Alternative idea...

can the plugin broker, if it is asked for a version that doesn't exist... simply grab /latest as a fallback behaviour? Better that than:

  • forced hardcoding of old versions / dead boilerplate code
  • breaking compatibility when we forget to push 7.y.z+1 versions into master

@ibuziuk
Copy link
Member

ibuziuk commented Dec 10, 2019

Should these old versions be marked deprecated/auto-update to the latest? Compatibility is good but so is staying current w/ 7.x.next

I believe we should follow the flow we had since the very beginning related to backward compatibility.

can the plugin broker, if it is asked for a version that doesn't exist... simply grab /latest as a fallback behaviour? Better that than:

yes, there is an rh-che issue for that redhat-developer/rh-che#1396
I thik we need to create an upstream issue for that. In any case I think this should not block this PR from merging

@nickboldt nickboldt self-requested a review December 10, 2019 16:08
@nickboldt nickboldt merged commit f6bd1b8 into eclipse-che:master Dec 10, 2019
@nickboldt
Copy link
Contributor

Agreed, merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Latest plugin registry does not include theia/machine-exec versions 7.3.2, 7.3.3
3 participants