<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Good day!<div><br></div><div>This is just a reminder that branching for the 3.4 release will occur at this time:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><span style="background-color: rgb(255, 255, 255); color: rgb(69, 69, 69); font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 19px; text-align: left; ">Monday, November 18, 2013 at 7:00:00 PM PST / </span><span style="background-color: rgb(247, 247, 247); color: rgb(69, 69, 69); font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 19px; text-align: left; ">Tuesday, November 19, 2013 at 3:00:00 AM UTC</span></div><div><br></div><div>What this means for you!</div><div>------------------------</div><div><br></div><div>* Please keep the release notes up to date -- There has been very few commits to them. Please be proactive and update them with any significant feature that was put in.</div><div><br></div><div>* Keep the tree healthy -- Pay attention to buildbot failures and regressions and fix them as quickly as possible.</div><div><br></div><div>* Finish your features -- The 18th won't be the final day to submit code, but you should have a significant portion of the feature finished by then. I.e., a few minor changes, bug fixes, and clean ups. If you're going to be late with your feature, please let me know ahead of time and we can figure something out.</div><div><br></div><div>* Fix bugs -- Go through the bug database and find those PRs which you can fix easily. If a PR is a release blockers, then ask the code owner to bump up the priority.</div><div><br></div><div>This should be a wicked awesome release! :-)</div><div><br></div><div>Share and enjoy!</div><div>-bw</div><div><br></div></body></html>