Merge ~bettyl/plainbox-provider-checkbox:modify-bluetooth-file-transfer into plainbox-provider-checkbox:master
Status: | Merged |
---|---|
Approved by: | Jonathan Cave |
Approved revision: | 21a7467ec3e8aca9a7d3fae27bcae838b6f2cde8 |
Merged at revision: | f8119c41ec8f9fa7eee504da92d48865cdd9cdc2 |
Proposed branch: | ~bettyl/plainbox-provider-checkbox:modify-bluetooth-file-transfer |
Merge into: | plainbox-provider-checkbox:master |
Diff against target: |
37 lines (+9/-5) 2 files modified
units/bluetooth/jobs.pxu (+8/-4) units/bluetooth/test-plan.pxu (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Maciej Kisielewski | Approve | ||
Betty Lin (community) | Needs Resubmitting | ||
Pierre Equoy | Approve | ||
Review via email: mp+370350@code.launchpad.net |
Description of the change
Confirm the "bluetooth/
u@u-Precision-
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
com.canonical.
Looks good to me!
Just one minor thing: `_description:` is the old way of writing manual jobs purpose/ steps/verificat ion. Instead, it's better to use `_purpose`, `_steps` and `_verification`.
So something like
------- ------- ------- ------- -- ------- ------- ------- --
_description:
PURPOSE:
Bla bla bla
STEPS:
1. One
2. Two
3. Three
VERIFICATION:
Does it work?
-------
Can be written:
------- ------- ------- ------- -- ------- ------- ------- --
_purpose:
Bla bla bla
_steps:
1. One
2. Two
3. Three
_verification:
Does it work?
-------
(not that in the second case, `_description` is gone)