1. Review the merge request. If you see anything questionable, kick it back to "needs review" or "needs work", unassign it from yourself, and leave a comment. If the patch introduces changes that need manual updating from site admins, be sure that the issue summary has a release note.
1. Review the merge request. If you see anything questionable, kick it back to "needs review" or "needs work", unassign it from yourself, and leave a comment. If the patch introduces changes that need manual updating from site admins, be sure that the issue has a change record associated with it. Also be sure that tests are passing; don't merge an issue with failing tests unless there's a documented reason why you need to in this case.
2. If it looks good, go through the issue and assign credit as you see fit.
3. If it looks good, go through the issue and assign credit as you see fit.
3. Adjust the issue title as desired for maximum clarity, since it will be the commit message.
4. Adjust the issue title as desired for maximum clarity, since it will be the commit message.
4. Save changes to the issue.
5. Save changes to the issue.
5. Scroll to the bottom of the issue and merge it.
6. Scroll to the bottom of the issue and merge it.
6. If you're going to backport the issue to the current release branch, read on; otherwise, leave a nice comment and mark the issue fixed -- you're all set.
7. If you're going to backport the issue to the current release branch, read on; otherwise, leave a nice comment and mark the issue fixed -- you're all set.
