Hey Chris, list, > I don't mean to be a pain, perhaps I'm misunderstood. I mean, lets > quit talking about how we should talk about this, and instead just > start talking about changes we could make.
Yeah that sounds much better, let’s start talkin … I like the questions you brought up in your mail. And I would propose to ask for more … like a distributed brainstorming using e-mail. Maybe we could do it across multiple lists. We can ask for questions, ideas and no-goes (so called ''brainstorming paradox'') and no discussion. And we need additional resources/ a strategy to involve adopters in the QA process. We couldn’t put everything on the shoulders of our brave developers. Beside this I look at the wiki to figure out, what are our current processes regarding release and qa but I’m not sure if there is a documentation of the current process. Do we have this somewhere in the wiki or might this be an additional task we have to do? > In otherwords, I agree we need process changes to catch these errors, so > can we get on with trying to make those changes instead of trying to > figure out who is to blame for the bugs? Sorry if it was not clear but I didn’t want to blame someone, I want to figure out why this happens to understand the problem. My first impression is that there are a bunch of things that came together and we should list them to resolve them before we start our next release process. Nils > > Chris > -- > Christopher Brooks, BSc, MSc > ARIES Laboratory, University of Saskatchewan > > Web: http://www.cs.usask.ca/~cab938 > Phone: 1.306.966.1442 > Mail: Advanced Research in Intelligent Educational Systems Laboratory > Department of Computer Science > University of Saskatchewan > 176 Thorvaldson Building > 110 Science Place > Saskatoon, SK > S7N 5C9 > > _______________________________________________ Matterhorn-users mailing list [email protected] http://lists.opencastproject.org/mailman/listinfo/matterhorn-users
