router

router copied to clipboard

Two improvements on our current release checklist:

• The release PR body should contain the relevant changelog, this allows for easier markdown check / changelog review before approval.
• The release section after a release has been cut should contain only the relevant changelog section, thus avoiding history cycles in the releases summary page

This might be a right opportunity to talk about the merge policy (who gets to merge? how many approvals are required?) as this is something @bnjjj asked me and we couldn't find any mention of that