Nick Boldt

Results 110 comments of Nick Boldt

For downstream developer images (UDI) see https://issues.redhat.com/browse/CRW-2463 and https://issues.redhat.com/browse/CRW-2464 (requires https://github.com/eclipse/che/issues/19953 ) If upstream is not multiarch (because we can't use buildx on Z) that should not prevent downstream from...

Downstream no longer has to split between TP and GA as we have added labels into the dashboard. There are also no openj9 images anymore. https://github.com/eclipse/che/issues/20799#issuecomment-1194054260 So while we still...

Seems this is now fixed in master as neither EclipseLink 2.7.5 or 2.7.6 were signed. https://git.eclipse.org/c/eclipselink/eclipselink.releng.git/tree/promote.sh#n373 vs https://git.eclipse.org/c/eclipselink/eclipselink.releng.git/tree/promote.sh?id=5007eba861dd3e51e8cb8ae98302fffa04dfc8cc#n372 That being said, we can't include non-signed artifacts in the Eclipse Simultaneous...

Verified and blogged about it too. https://divby0.blogspot.com/2020/02/fedora-31-rawhide-in-windows-subsystem.html

So you're saying to use `.vscode/recommendations.json` for ONLY vscode, you can also add an empty `che-theia-plugins.yaml` file?

Adding a compliance check would be cool, but I still won't be able to pass pretty strings to the Dashboard UI. And even if you clean up the passed in...

First two PRs: * https://github.com/eclipse-che/che-plugin-registry/pull/1441 * https://github.com/redhat-developer/devspaces/pull/829 Once merged, will need a PR for Dashboard too, as we'll hit this error: ``` displayName must conform to lowercase RFC 1123 subdomain...

I think we can resolve this as we have updated the display names in the dashboard and can still open workspaces. See https://issues.redhat.com/browse/CRW-3098

Suggested solution based on chat today w/ Artem: - [ ] add a new make-release.sh script (similar to what's in machine-exec?); this will - [ ] create a branch every...

@svor @azatsarynnyy Do we need to also update https://github.com/eclipse-che/che-plugin-registry/blob/main/che-editors.yaml to point to released che-code images & tags, or just stick with "insiders" ?