Clock

This documents the expections that the project has on what both submitters and reviewers should ensure that they've done for a merge into the project.

MP Submission Checklist Template

Note: Please ensure you include the following form filled out and submitted along side your code to the MP ticket.

  • Are there any related MPs required for this MP to build/function as expected? Please list.
  • Is your branch in sync with latest trunk? (e.g. bzr pull lp:ubuntu-clock-app -> no changes)

  • Did the tests run successfully (QML and AP)?
  • Did you perform an exploratory manual test run of your code change and any related functionality?
  • What device (or emulator) has your component test plan been executed successfully on?
  • If you changed the UI, was the change specified/approved by design?
  • What manual tests are relevant for this MP?
  • If you changed UI labels, did you update the pot file?
  • Did you include a link to the MR Review Checklist Template to make your reviewer's life easier?

MP Review Checklist Template

Note: Please ensure you include the following form filled out and submitted along side your code to the MP ticket.

  • Have you checked that the submitter has accurately filled out the submitter checklist and has taken no shortcuts?
  • Did you run the manual tests listed by the submitter?
  • Did you do exploratory testing related to the component you own with the MP changeset included?
  • If new features have been added, are the manual tests sufficient to cover them?

MP Landing Checklist Template

  • Ensure that the checklists have been properly filled out by submitter and all reviewers

Process/Merges/Checklists/Clock (last edited 2014-09-08 23:46:53 by nik90)