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

Retest and unify all devfiles with samples #13863

Closed
sparkoo opened this issue Jul 16, 2019 · 3 comments
Closed

Retest and unify all devfiles with samples #13863

sparkoo opened this issue Jul 16, 2019 · 3 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. 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. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.

Comments

@sparkoo
Copy link
Member

sparkoo commented Jul 16, 2019

Is your task related to a problem? Please describe.

We have ~20 devfiles with samples and it is the first thing that new user will probably try and see in Che, thus user experience here is critical. Along the way of creating these devfiles, several issues were created and fixed (#13796, #13823, #13592, and probably more). These might cause new issues in already merged devfiles.

Describe the solution you'd like

After all agreed devfiles are merged #13529, we should retest them all, unify them (names, descriptions, tasks) and address all user experience issues. User experience must be as smooth as possible.

Describe alternatives you've considered

do nothing

Additional context

this is follow-up of #13529

@sparkoo sparkoo added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jul 16, 2019
@l0rd
Copy link
Contributor

l0rd commented Jul 16, 2019

This issue doesn't look like a "new issue" but rather as a subtask of #13529 that you would like to include in 7.0.0. Is it correct @sparkoo?

@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. team/platform status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering. labels Jul 16, 2019
@sparkoo
Copy link
Member Author

sparkoo commented Jul 17, 2019

@l0rd I thought of it as a follow-up task. But might be a subtask as well.
I'd like to include this to 7.0.0 as I believe user experience here is critical. However, I'd like to hear yours and others opinion, whether it is really needed to do.

@skabashnyuk skabashnyuk added the severity/P1 Has a major impact to usage or development of the system. label Jul 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement A feature request - must adhere to the feature request template. 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. status/info-needed More information is needed before the issue can move into the “analyzing” state for engineering.
Projects
None yet
Development

No branches or pull requests

3 participants