Split out reserved security policies from regular ones
Bug #1227814 reported by
Martin Albisetti
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| qtcreator-plugin-ubuntu |
Fix Released
|
High
|
Juhapekka Piiroinen | ||
Bug Description
The new security policy group selection is filled with awesome, thank you.
However, we'd liked to very clearly distinguish regular policies from restricted ones, probably by burrying the restricted ones in the UI a bit more, maybe collapsed in a separate list, with a clear warning that their app will likely get rejected when it's expanded.
Related branches
lp:~juhapekka-piiroinen/qtcreator-plugin-ubuntu/fix-bug-1232213
- Zoltan Balogh: Approve
- PS Jenkins bot: Approve (continuous-integration)
- Timo Jyrinki: Needs Fixing
-
Diff: 300 lines (+102/-49)9 files modifieddebian/changelog (+6/-0)
share/qtcreator/ubuntu/menu.json (+28/-29)
share/qtcreator/ubuntu/scripts/i18n_update_template (+42/-0)
share/qtcreator/ubuntu/scripts/qtc_project_click_create (+2/-2)
src/ubuntu/ubuntumenu.cpp (+3/-2)
src/ubuntu/ubuntupolicygroupinfo.cpp (+1/-1)
src/ubuntu/ubuntupolicygroupinfo.h (+2/-2)
src/ubuntu/ubuntusecuritypolicypickerdialog.cpp (+8/-3)
src/ubuntu/ubuntusecuritypolicypickerdialog.ui (+10/-10)
Revision history for this message
| Jamie Strandboge (jdstrand) wrote | #1 |
| Changed in qtcreator-plugin-ubuntu: | |
| assignee: | nobody → Juhapekka Piiroinen (juhapekka-piiroinen) |
| status: | New → Confirmed |
| importance: | Undecided → High |
Revision history for this message
| Juhapekka Piiroinen (juhapekka-piiroinen) wrote | #2 |
| Changed in qtcreator-plugin-ubuntu: | |
| status: | Confirmed → Fix Committed |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #3 |
| Changed in qtcreator-plugin-ubuntu: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
You can do this by parsing the "# Usage:" string in the policy groups. Things that are "common" should be easily usable, anything else could be hidden in some way. I don't think this is super high-priority because the information is already available on the right. And, YES, thank you for the update. :)