Unity8

Differences between revisions 31 and 32
Revision 31 as of 2014-09-02 13:03:46
Size: 2548
Editor: c-174-63-86-112
Comment:
Revision 32 as of 2014-09-29 11:35:56
Size: 2618
Editor: HSI-KBW-109-193-027-090
Comment:
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:
 * Did you make sure that the branch does not contain spurious tags?

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
  • Copy & paste the checklist into MP description

  • Use strip-u8-tags.py if applicable

  • Make sure you have set a commit message. Commit messages should have the following format:
    • A single-line summary or short description of the change (something no longer than 80 or 90 chars)
    • Follow-up lines explaining the change in a bit more detail if needed (make sure not to leave an empty line, just use one line break here). Make sure to mention things like new dependencies, bug numbers, or anything else that an outside developer or user might be interested in. This all ends up in debian/changelog.
    • An empty line (if you're going to have this next section).
    • An even more complete explanation, if needed. This will not go in debian/changelog, but will go into bzr. So more detailed comments about reorganizing code or similar would be appropriate here.
  • Questions to answer:

 * Are there any related MPs required for this MP to build/function as expected? Please list.
 * Did you perform an exploratory manual test run of your code change and any related functionality?
 * Did you make sure that your branch does not contain spurious tags?
 * If you changed the packaging (debian), did you subscribe the ubuntu-unity team to this MP?
 * If you changed the UI, has there been a design review?

MP Review Checklist Template

  • If you have been asked to review and are not on the unity-team, please review for any interdependency and paste the associated MP reference in a comment
  • Ensure the commit message has the proper format (see above)
  • Copy & paste the checklist into MP review comment

  • Questions to answer:

 * Did you perform an exploratory manual test run of the code change and any related functionality?
 * Did CI run pass? If not, please explain why.
 * Did you make sure that the branch does not contain spurious tags?

MP Landing Checklist Template

  • Questions to answer:
    • Is the MP approved by at least 1 member of unity-team?
    • Are the approvals equal to or greater than the disapprovals?
    • Is the checklist completed to satisfaction?
    • Has the TestPlan been executed successfully on emulator, N4?

Process/Merges/Checklists/Unity8 (last edited 2017-03-28 21:55:58 by saviq)