Do we have any goals before we release the next beta?
Maybe a feature freeze is in order to get a newer beta out?
Grabbing the head from SVN will probably never be bug free but I know I and many others are using it in a "production" environment which is never a great idea. If you are doing it this way, probably the best thing you can do is constantly grab the latest source.
Robin and any other devs are impressively responsive to fixing problems we find and discuss on here.
Maybe we should make a list of features that need to be finished before the next beta and once those are knocked out set a bug-scrub day or two where everyone combs over everything to find any remaining issues.
Matt
Pim Vullers wrote:
Robin Elfrink wrote:
But then again, latest SVN is _not_ a released version.
Robin
Reaction 1: I fully agree with that. But in my opinion trunk should still have correct existing functionality, and as I said before it's alright that new things don't work as long as old functionality doesn't get broken.
Reaction 2: Indeed it isn't, however it also isn't a working copy.. that should be the checkout on your system.
Reaction 3: For other developers it would be nice if things don't get broken every time.
Sorry for this strange way of reacting but I couldn't get Right in just one way. (Perhaps because English isn't my native language. Or just because I want to say to much :).)