Our team had requested that we let the forum know the what and why's behind the lack of information.
We've moved to a much more structured approach and July was a major internal milestone for us. This milestone gets reviewed next week, and the results of that review will be released as a devblog. This will give more information to everyone about where the project is at and where it is going.
Why the lack of information?
Development pace has been very rapid and as information gets prepared for a devblog, inevitably things change. Furthermore, things get fixed and added at different times - so it means it is hard to find a time when everything is committed at once.... except for milestones. Hence, we will be releasing the devblog based on the milestone review.
Does this mean it the public alpha is beginning?
No, it does not. But what it does mean is that next week, you will be fully briefed on the current milestone and the steps from there onwards.
Why do this?
We realize that the community are stakeholders in the development, and we've been trying to come up with a method for providing information that works within our development process. We are now at the point where we can follow this. Interest has gotten... rather agitated lately and I think the best thing is to provide some clarity as to our process for next week and beyond.
Seriously though, does this mean the alpha is happening?!
No, it does not. There is no set release date. When an alpha candidate passes it's milestone review, it will be released.