Hi all, While work is underway to get a 3.4.6 release out the door, I was thinking of helping out as release manager for 3.5.0. Here's a rough plan to getting it done:
For 3.5.0 there are 262 unresolved issued. Some of them are pretty ancient so maybe the available patch doesn't apply cleanly or doesn't apply at all. For the easy/clean cases I can check if tests are good, do another review (if necessary) and ping the commiter who last touched the related files or logical section to get another glance and hopefully a commit. In parallel, for the ancient patches which don't apply cleanly and need a lot of work we can decide on punting for 3.5.1 depending on how critical or not they are. And we can reiterate here until we get a tractable list of issues for 3.5.0. After a first iteration/triage we'll have a better idea of the amount of work left and we can come up with a potential release date and eventually commit ourselves to that. We'll also need to pay special attention to ensure that the migration path from 3.4.6 to 3.5.0 is smooth. Does it sound reasonable? If it does, I'll start with the triage so prepare yourself to see some activity in JIRA :-) Cheers, -rgs
