Hi all, (tl;dr: Get cracking on v3.3.5 bugs, and fix/close/move stuff asap!).
I'd like to prepare the v3.3.5 release on Friday this week. Anything left in v3.3.5 by the end of business day Friday would then be moved out to v3.3.6 (and probably therefore, v3.5.0). This puts us at a release date for v3.3.5 for 7/24, and hopefully v4.0 about 2 weeks after that. For the records, this is over 2 months later than planned.
After v3.3.5 is released, only the most severe of bugs would be accepted for the v3.4.0 release. As part of this, I would therefore also branch v3.4.0 on Friday evening (PST). However, everyone needs to spend the next couple of weeks doing as much tests on these releases, to make sure v3.4.0 is not a dud going out the door prematurely.
Can we make it? -- Leif
