On Friday 29 January 2010, Edgar Grimberg wrote: > > Right now I seem to be the person doing this for the bugs > > that can (or should!) affect the 0.4.0 release; nobody > > volunteered to handle *any part of that* for the community. > > Since I'm doing some testing these days, sign me up as a volunteer for > the bug database.
Thanks! As I said elsewhere, I'll wait till Tuesday eve (PST) for additional feedback before doing anything with Trac. Right now it sounds more likely to happen than not, with at least a handful of folk willing to help make it happen. Assuming I do turn it on, I think we'll try an RC2 as a dry run. Maybe we can fix some of those bugs you've uncovered. :) > > ... And as far as I can tell, this is the first release > > cycle that's even had lists of bugs/regressions like that. > > I have a list of test cases that were run (by me and Laurentiu Cocanu) > on v0.4.0-rc1. I'll send a patch in a moment. That's good. But to be clear, having regression tests is not what I meant (though it's extremely important for any reproducibility of quality). I was meaning more like "periodic status updates with specific reference to unresolved regressions and other open bugs". - Dave _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
