I think we all understand that things are Done "When it’s done".
I doubt anyone has an issue with that.
The issue I have is "we don’t know how long that’ll take just yet".

We moved to an agile methodology, Scrum specifically, for 3.5 and 3.6, because the previous 4 releases were (respectfully) fairly poorly project managed (and all released late). Obviously, this has gone out the window, or never properly implemented in the first place. We're at the stage where a 3 month dev cycle is now at 5 months, and closing in on 6 months. An underestimation of work by 100% scares me as a project manager. But then, the view of core devs is:

"nonsensical project management stuff" is "completely meaningless to real-world software development"
Otto - http://make.wordpress.org/core/2013/04/23/post-formats-schedules-and-philosophy/#comment-8599

The specifics of the delay are 3.6 are not the issue. The lack of communication and planning are the issues. The project schedule was changed with no tweet, irc, blog post, or comment on make./core, with the old version removed. Communication and Openness? Yes? Yes.

It takes 30 seconds, to send a tweet once a week saying "We're estimating the release date as XX/XX, confidence is 60%".

WordPress has some genuinely amazing developers, who continue to do simply incredible work. There does come a point in time where we have to realise that developers alone are not enough (It's why we now have UX, Designers, and Accessibility folks). Project Management is a unique skill-set. Just because someone is an amazing developer, does not automatically make them an amazing project manager, or tester, or bus driver, or butcher, or soccer player, or president. Maybe it's time we embraced it the whole way through a release cycle, and not just throw it out the window when it gets to the parts we don't like.

Maybe thats 15 years of project management talking though...