The third, and next-to-last, beta snapshot planned for the 3.6 release cycle is coming up in a few days. With fewer than 7 weeks remaining until the 3.6.0 release, it is very important that we all focus on stability and correctness. Please try to make sure that all remaining non-doc issues associated with new features are addressed in b3. Any remaining 3.6 feature-related issues still open after b3 should be marked in the issue tracker as "release blocker" and *must* be addressed one way or another by b4, 11-21. All other non-critical bug fixes should also be checked in by b4. Only release critical and doc fixes will be allowed once we exit the beta phase. Please plan accordingly.
Please contact me if you have any questions about the 3.6.0 schedule or about whether a change is appropriate at this point in the 3.6.0 cycle.
To recap, the remaining milestones for 3.6.0:
2016-10-31, 1200 UTC: 3.6.0 beta 3 (feature fixes, bug fixes, doc fixes)
2016-11-21: 3.6.0 beta 4 (important bug fixes and doc fixes)
2016-12-05 3.6.0 release candidate 1 (3.6.0 code freeze, release critical bug fixes, doc fixes)
2016-12-16 3.6.0 release (3.6.0rc1 plus any necessary emergency fixes)
Thank you all again for your efforts so far on 3.6!
-- Ned Deily email@example.com --