[Tails-dev] New review'n'merge process

Hi,

at the summit, we've got ourselves a new process to ask for
review'n'merge, and track such requests. The idea is to make it easier
for non-RM's to do part of this work.

The relevant bits of this policy have been integrated into
[[contribute/merge_policy]]. Here's the full version:

1. When a contributor flags a ticket as "Ready for QA", one must
assign this ticket to nobody (aka. unassign it from themselves) by
default. Unless it's clear to this contributor that the current RM
won't be able or willing to do this specific review; in that case,
the branch contributor shall try to find someone else to do the
review, and assign the ticket to them.

2. The RM is still the fallback for reviewing'n'merging stuff
relatively promptly. If a ticket is flagged "Ready for QA", but the
RM cannot or doesn't want to take care of the review'n'merge, it's
the RM's responsibility to ask for help. The "Release Manager View"
is probably the best place to track such tickets.

3. When someone starts doing a review'n'merge, they must assign the
relevant ticket to themselves, in order to avoid duplicated work.

Cheers,
--
intrigeri