UX review minor/major

[PVince81]

Following #391 there were some UI changes.

Would be good to get a UX and design review for the changes to see if they fit.

cc @pmaier1 fyi

[PVince81]

some screenshots here: #387 (comment)

[PVince81]

• clarify CLI messages: Refactor the app to allow choosing between next minor and major update #391 (comment)

[davitol]

Running upgrade command with --major option when there's no major option available, should the command install the minor version or refuse the upgrade?

[PVince81]

As an admin, I'd say whenever I specify --major mostly means I want to "update all the things to the latest whatever". When I don't specify it, it means "safe update to the latest minor".

So if there is no major and --major is specified, I'd say also update to the latest minor if no major exists.

@VicDeo @pmaier1 @DeepDiver1975 thoughts ?

[VicDeo]

As for me: we have a limit until --major is specified. --major option removes this limit.
So it is expected.
As I already wrote I don't like the idea of splitting to minor/major at all...

[felixheidecke]

I'd recommend using the same UI for updating in the details view as well as on the update page.
See: #391 (comment)

Namely having the action be the name of the button (update to 1.0.0) along with the drop-down.
Also color diff while hovering over the button with the caret, ist nice. Should be consistent across the whole button.

I can take care of that if you like.

[PVince81]

@felixheidecke please take care. if the current UI isn't too bad let's keep the UX improvements for the new market app release (0.3.1).

[PVince81]

please PR to release-0.3.0 branch, unless you think the current UI is ok for the release

[PVince81]

we should fix the occ command however @VicDeo

[VicDeo]

@PVince81 yep. #424

[PVince81]

@felixheidecke I need your feedback here to decide whether to wait longer for UX tweaks or if I should go ahead with RC2 + final

[felixheidecke]

The current UI is "okay" but not nice. We can go ahead and release it. About 2hrs to fix.