If you’ve been watching Core trac and the proposed schedule then you would have known that Beta 1 was supposed to be done today. Not a big deal but’s it’s important to know why, as Mark Jaquith explains:
Our original schedule had us hitting beta 1 today, March 13th. We’re not quite there. Beta should mean that we’re feature complete, and we’re not.
We could do what we’ve done in the past, and declare a beta, while continuing to do feature work, but that just devalues the meaning of “beta”. I want people in the WordPress ecosystem to trust that when we say “beta”, that means we’re feature complete and that they should start seriously testing their themes and plugins against trunk for issues.
If we continue with feature development during the beta period, that will just shove back everyone’s testing to the RC period, which will translate to more issues going unnoticed and tarnishing the release.
Love the honesty and transparency – and know one’s honestly going to cry over spilt milk.
The result is that things will push back 2 weeks til March 27th and then the release to 29th. And besides, all of us are incredibly busy right now, right? We’re busy creating content, building great WordPress products, plugins, apps, and themes. Some of us are busy handling our clients with the last major update!
So we’re good. As you were. Thanks Mark for the update!
Start the conversation