Comment 3 for bug 326079

FWIW, I think setting the Reply-to header in notification emails to an appropriate review destination is fairly common practice. Each project can decide what the right destination is: if that branch has a review team, then that might be the place, or sometimes there's a single mailing list the entire project uses for reviews. (I'm aware that this is getting into new UI work, so it might make sense to come up with reasonable defaults now, and deal later with the question of providing UI to choose alternatives to those defaults).

Making it be the review team of the branch will encourage people to set up teams with mailing lists for this purpose, which might be a good thing anyway.