Just a quick reminder that feature freeze is about seven days away, Sept 1.  You should be wrapping up all remaining reviews and tests and assertively stabilizing your features.   Specifically, you should be avoiding crash landings a day before the freeze.  You do this by:

* Landing your features early on a project branch (if appropriate), making sure it works on all platforms, passes all tests.
* Preparing QA for your feature by letting them know what needs to be tested, how to better exercise corners of your code that might be overlooked, and letting people know how to provide valuable feedback (i.e., if running D2D, make sure you submit driver information contained in about:support, etc.)  If you need help here, ask.
* Picking up the phone to call slow reviewers--I'm serious here.  Don't wait until the last minute.
* Letting interested parties/dependencies know when you intend to land so that people are prepared and know how to help (i.e., let the sheriff-on-duty know in advance that you need a slot to land, if appropriate), etc.
* Reach out for help early (it's already late!) if you run into trouble.
* Pay attention to the tree once landed and immediately address regressions or bustages.  There is no time for long delays due to tree jams!

Sincerely,

Damon