I had a question about this point on that page:
> Set the target milestone (unless an aurora migration is due within 24
What is the rationale behind having this set when landing on inbound?
Does it make more sense for the target milestone to be set when m-i is
merged to m-c, and we know for sure which version it ended up in?
A couple of times I've landed something on inbound just before an aurora
migration and had to update the target milestone because it ended up on
the next train. Also, if a patch is backed out the target milestone is
un-set, so it seems reasonable to me that it should only get set once,
when the patch "sticks" and gets into m-c.