Shareth wrote:Why don't just release 0.7 with base functionality and then upgrade from there?
The issue with making a 0.7.0 release now, is that the ongoing development is going to require further interface changes - on top of what's already been done. This means that we make the 0.7.0 release, everybody updates their code (and perhaps 3rd parties rewrite their renderer modules) to work, then we make the 0.7.1 release, which changes many things an breaks the interfaces requiring everybody to update their code again, then we do the same again with 0.7.2 and so on - this is unacceptable to me, and I feel that it would be unacceptable to many others also.
Shareth wrote:This way it'll get way more testing and a lot more bugs will be fixed. Also might highlight some design/implementation problems earlier.
We have the code in a public SVN repository for this purpose. I'm not trying to be funny by saying that, I do understand the POV of those people wanting a quick release of this code, but it's just not ready. The way to look at it is that if people are unable or unwilling to check the code out of SVN and build it, then they are definitely not ready to use the code in it's current state.
One thing I do want to look at is unstable development snapshot releases (source and binary packages) - though I want that to be a fully automated process, but I've not looked into getting that under way yet.