Unity8
Differences between revisions 9 and 10
|
Size: 2120
Comment:
|
Size: 919
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
| * Is your branch in sync with latest trunk (e.g. bzr pull lp:trunk -> no changes) * Did you build your software in a clean sbuild/pbuilder chroot or ppa? * Did you build your software in a clean sbuild/pbuilder armhf chroot or ppa? * Has your component "TestPlan” been executed successfully on emulator, N4? * Has a 5 minute exploratory testing run been executed on N4? * If you changed the packaging (debian), did you subscribe a core-dev to this MP? * If you changed the UI, did you subscribe the design-reviewers to this MP? * What components might get impacted by your changes? * Have you requested review by the teams of these owning components? }}} |
* Answers to checklist questions are desired to be 'yes' but if 'no' or 'not applicable' please expound * First please copy & paste into the MP the checklist found at https://wiki.ubuntu.com/Process/Merges/Checklists/Common * Did you break mir server API or ABI and have the relevant bumps to .so and debian docs been made ? * Did you break mir client API or ABI and have you followed up with the known clients & announced on mir-devel mailing list ? }}} |
| Line 19: | Line 14: |
| {{{ Note: Please ensure you include the following form filled out and submitted along side your code to the MP ticket. Note: A Reviewer usually is responsible for a single component; since we ask for reviewers to be subscribed that might see an impact by this MP this mean that we get one-to-many reviewers contributing to the MP review process. Below the checklist that a reviewer should follow taking the viewpoint of his component, which might or might not be the same as the component this MP is targeted against. * Are any changes against your component pending/needed to land the MP under review in a functional state and are those called out explicitly by the submitter? * Did you do exploratory testing related to the component you own with the MP changeset included? * Has the submitter requested review by all the relevant teams/reviewres? * If you are the reviewer owning the component the MP is against, have you checked that submitter has accurately filled out the submitter checklist and has taken no shortcut? }}} |
Simply refer to https://wiki.ubuntu.com/Process/Merges/Checklists/Common |
| Line 32: | Line 17: |
| * ensure that the checklists have been properly filled out by submitter and all reviewers | Simply refer to https://wiki.ubuntu.com/Process/Merges/Checklists/Common |
MP Submission Checklist Template
Note: Please ensure you include the following form filled out and submitted along side your code to the MP ticket.
* Answers to checklist questions are desired to be 'yes' but if 'no' or 'not applicable' please expound * First please copy & paste into the MP the checklist found at https://wiki.ubuntu.com/Process/Merges/Checklists/Common * Did you break mir server API or ABI and have the relevant bumps to .so and debian docs been made ? * Did you break mir client API or ABI and have you followed up with the known clients & announced on mir-devel mailing list ?
MP Review Checklist Template
Simply refer to https://wiki.ubuntu.com/Process/Merges/Checklists/Common
MP Landing Checklist Template
Simply refer to https://wiki.ubuntu.com/Process/Merges/Checklists/Common
Process/Merges/Checklists/Unity8 (last edited 2017-03-28 21:55:58 by saviq)