@Ipstenu:

But that’s what I’m saying. Many of the issues people are experiencing now were known long before.

The issue with plugins that replace/extend the wpdb class was known. (I asked myself about it at the dev IRC channel, at the time the first changes in wpdb were made, and nacin replied then and explained why it was happening.) The memory exhaustion issue was known. There was even a whole, long ticket dedicated to it. The stuck-in-maintenance-mode issue must have been known too. (I experienced it myself a couple of times while testing, but can’t recall if I mentioned it or reported it officially.) The HeadSpace2 issue was known. (I had myself a discussion about it with ocean90 on the dev channel a few weeks ago.)

And these are just the issues that had come to my personal attention. (I follow wp development, and I have 3 live sites running on trunk all the time. So, I see quite a few issues first-hand, but I do not see, and no single person can see, every issue that may be expected in every configuration. That’s where the collective experience of testers and contributors comes in: with so many people involved, we can reasonably expect to be aware of all serious issues that may be expected in common configurations.)

So, if there are issues that are known, why not make a list of them before the final release, instead of waiting to make a sticky thread after the release?

Demetris
http://op111.net/76 ‹ See what is new in WordPress 3.0!