...

Communicating about the merge

Wiki MarkupSend an email with a "\[MERGE\]" tag in the subject line to the dev list.  It It's useful to point to the design doc on the wiki, the jira record for the work, and any of the critical discussions that talk about the changes.  The reason for an email like this is to help the community understand what the changes will be.  Because of this goal, pointing to the commit-sh in master that tells everyone what point in the master tree they should use to compare the branch with.  Seeing a clean diff is critical to reviewing the proposed  The reason for an email like this is to help the community understand what the changes will be.  Because of this goal, pointing to the commit-sh in master that tells everyone what point in the master tree they should use to compare the branch with.  Seeing a clean diff is critical to reviewing the proposed merge.

Once you send that email, wait for feedback for at least 72 hours!

...