Issue triage 12.7.2019

## Summary

## New Blockers (1)
https://github.com/eclipse/che/issues/13823 - Go sample `permission denied` issues with dependencies

## Issues Added to 7.0.0 (1)
https://github.com/eclipse/che/issues/13828 - chectl workspace:start fails for multi-user Che

## Issues added to 7.1.0 (1)
https://github.com/eclipse/che/issues/13832 - Apache Camel devfile not starting on Hosted Che

## Issues added to 7.x (3)
https://github.com/eclipse/che/issues/13827 - Decouple Java selenium E2E tests from GWT-code
https://github.com/eclipse/che/issues/13824 - chectl devfile:generate could show the command that have been used in the generated file
vhttps://github.com/eclipse/che/issues/13830 - Uncaught error after terminal widget creation

## Backlog (6)
INFO NEEDED - https://github.com/eclipse/che/issues/13826 - Empty Warning displayed
PM/Architect input required - https://github.com/eclipse/che/issues/13834 - Persist installed VS Code extensions
PM/Architect input needed - https://github.com/eclipse/che/issues/13835 - Investigate Native-Compiling jdt.ls
team/platform analysis - https://github.com/eclipse/che/issues/13821 - [Helm] warnings on booting keycloak
info-needed - https://github.com/eclipse/che/issues/13817 - devfile: dockerimage with command is not executing entrypoint
info-needed - https://github.com/eclipse/che/issues/13599 - Python language server failed to start

## Closed as duplicate (1)
https://github.com/eclipse/che/issues/13822 - multi user deploy failed...

can you please add eclipse-che/che#13838 to the triage? it's impacting many versions and che is not deploy-able on kubernetes environment

can you please add eclipse/che#13838 to the triage? it's impacting many versions and che is not deploy-able on kubernetes environment

Hi @SDAdham, I think I've reproduced this issue... I've tagged team lead of the responsible team in the issue. Hopefully they will take a look at this on monday and prioritize it accordingly.

Thanks @rhopp

Hmh..."blocker" is not really a term for the triage outcome. Should be 7.0.0, right? Also eclipse-che/che#13827 - Decouple Java selenium E2E tests from GWT-code should not be tagged 7.0.0. I'm not saying we can't work on it if we are confident the change is not breaking anything, but we can ship 7.0.0 without it.

I am puzzled as @tsmaeder for eclipse-che/che#13827: removing GWT tests because they are failing should be part of the release but not sure about ""rewrite Dashboard tests which use GWT-editor to check changes in Dashboard." I have commented that on the issue.

And yes for eclipse-che/che/issues/13823 we should specify if it will be included in 7.0.0 milestone or not (but it looks like it is and I am ok with it)

@l0rd - On the #13827 it's my bad. I was thinking about just making the code "compilable" - Sergii's draft PR was just disabling whole selenium module. On second thought that's perfectly fine for GA with me. I've commented on that issue and postponed it after GA.

@tsmaeder - Heh... I just copied some template from some previous triage. But now I cannot find the one... I may have added that by mistake. Anyway... It means the same as 7.0.0. milestone... I just thought it's bit more important - needs more visibility.