Was going to post this in our defect tracking system - bugtrack (I’ve used better, but BugTrack allows me to write cool XSL to process reports!). However, bugtrack systems shouldn’t be used to post opinions - so it goes here:
I was thinking after the last defect related to this particular CR, that the process could be refined. In particular, it seemed to me that a CR should be attached to a short presentation about the meaning of the CR and it’s point. Earlier a CR came through, which I expected to have massive consequences in the UI/WS and CMS - but Alan assured me that it was a small change relating on to the web. The point is that even with the best attempt to understand what is written on paper, it is often interpreted differently to what is required.
