Forum OpenACS Q&A: Response to Call for testers ... OpenACS 4

Collapse
Posted by Yon Derek on
I think that the crucial point in testing is fixing bugs that are reported. So the question is:
  • how to report bugs/small patches to make sure they get fixed
  • what is the plan for making sure that reported bugs get fixed
I know that the standard answer is "use sdm" but so far it isn't working.

I don't want anyone to take it personally, but that's a fact: 3.2.x was a disaster in this area (tens of bugs reported, many of them with clear descriptions and even patches; not many of them fixed). OpenACS 4 is heading into the same direction: there are already a few pages of bugs reported.

My point: there's little point asking for bug reports while there are still known bugs.

My second point: there must be a dedicated "sdm watcher", someone whose priority would be going through bugs in sdm and fixing them, closing invalid bugs etc. Otherwise sdm will become useless very quickly. Clearly not many people qualify for this position: this someone would have to have full cvs access and ability to close bugs in sdm.