Support #20907
closed
Ready to merge checklist template
Added by Peter Amstutz about 1 year ago.
Updated about 1 year ago.
Description
Write the template that developers should go through when posting a ready-to-merge note on a ticket.
- Description updated (diff)
- Assigned To set to Peter Amstutz
- Subject changed from Ready to merge checklist template to Ready to merge checklist template
Before asking for a branch review, please fill out this template with information about the branch.
template begins below, replace the bits between < >
<00000-branch-title> @ commit:<git hash>
<https://ci.arvados.org/... (link to developer test job on jenkins)>
Note each item completed with additional detail if necessary. If an item is irrelevant to a specific branch, briefly explain why.
- All agreed upon points are implemented / addressed.
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- Code is tested and passing, both automated and manual, what manual testing was done is described
- Documentation has been updated.
- Behaves appropriately at the intended scale (describe intended scale).
- Considered backwards and forwards compatibility issues between client and server.
- Follows our coding standards and GUI style guidelines.
<Additional detail about what, why and how this branch changes>
- Status changed from New to In Progress
- Status changed from In Progress to Resolved
Also available in: Atom
PDF
Updated by 
Updated by