Merge lp:~mterry/ubuntu-system-settings/interactive-while-locked into lp:ubuntu-system-settings
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Michael Terry | ||||
Approved revision: | 922 | ||||
Merged at revision: | 966 | ||||
Proposed branch: | lp:~mterry/ubuntu-system-settings/interactive-while-locked | ||||
Merge into: | lp:ubuntu-system-settings | ||||
Diff against target: |
178 lines (+92/-16) 4 files modified
debian/control (+1/-1) plugins/security-privacy/PhoneLocking.qml (+29/-8) plugins/security-privacy/securityprivacy.cpp (+48/-7) plugins/security-privacy/securityprivacy.h (+14/-0) |
||||
To merge this branch: | bzr merge lp:~mterry/ubuntu-system-settings/interactive-while-locked | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Sebastien Bacher (community) | Approve | ||
PS Jenkins bot | continuous-integration | Needs Fixing | |
Ken VanDine | Needs Fixing | ||
Matthew Paul Thomas | design | Pending | |
Review via email:
|
Commit message
Implement the "When locked, allow:" portion of the Security & Privacy panel, so now the user can control whether the launcher and/or indicators are available while locked. (LP: #1358340)
Description of the change
Implement the "When locked, allow:" portion of the Security & Privacy panel, so now the user can control whether the launcher and/or indicators are available while locked. (LP: #1358340)
The spec for this is here: https:/
And this needs to land and be tested with: https:/
== Checklist ==
* Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes)
- Yes
* Did you build your software in a clean sbuild/pbuilder chroot or ppa?
- Yes
* Did you build your software in a clean sbuild/pbuilder armhf chroot or ppa?
- Yes
* Has your component "TestPlan” been executed successfully on emulator, N4?
- Yes
* Has a 5 minute exploratory testing run been executed on N4?
- Yes
* If you changed the packaging (debian), did you subscribe a core-dev to this MP?
- I'm a core-dev
* If you changed the UI, did you subscribe the design-reviewers to this MP?
- Will do
* What components might get impacted by your changes?
- Security & Privacy only
* Have you requested review by the teams of these owning components?
- Who owns that?
Thanks, I've not reviewed it yet, but could you drop the translation template update from there? We don't do it from individual merge requests because it easily leads to conflicts, we rather commit manually an update after doing a landing that change strings