I agree with this, and furthermore, once it has stabilised often the kinds of fixes needed are no longer able to be done since there is a feature freeze on, at least that's been my experience. I've sat through entire cycles from alpha to gold and found major bugs that require more major rework but by the time someone looks at it, it's too late. I think we need a structure to adhere to that the developers also buy into so we know what to expect and where everybody stands. My advice, be prepared to argue, developers don't always see things the same way as the rest of mankind :)
Martin Schlander email@example.com 03/19/09 12:25 AM >>>
Tirsdag 17 marts 2009 18:23:53 skrev Alberto Passalacqua:
Any suggestion on how to start is more than welcome!
I think the first thing we need is for developers/packagers to drop a line here, when they think something is ready for serious widespread testing.
One big problem with the current situation is that noone knows what to test and when. One of the main reasons I usually don't test early alphas is that I expect everything to change dramatically later on anyway, hence thinking testing is probably pointless at that point anyway - but I guess some components _are_ ready for widespread testing and that point, we just need to know which.
Additionally maybe some automation could be set up where openfate would spam this list when a new feature reaches a certain status, so as to let us know it might be something that needed testing.