...
Second, I don't believe that the PC should be doing terribly much more than it has done so far later in the release cycle. For 90% of the decisions where the PC should play a role, if you have to ask for our input during QA, then we have probably already failed. Our main job is to make sure the homework is done coming into a release. Our job is more to prevent problems in development, QA and maintenance than it is to fix them once they arise.
_My sense is that we did an adequate, though not spectacular, job with 2.7. That said, I would like to hear more from the QA and maintenance teams specifically on the question of how well prepared the tools that we green lighted for inclusion in core were in terms of test planning, documentation, etc. On average, how confident are they that these tools have been designed and developed in ways that will make their jobs easier relative to the respective states the tools were in before they went through the PC process?
- What has been the net pay-off of the product council thus far. Is the Sakai 2 product better off? Sakai 3?
My sense is that 2.7 is better than it would have been, though again, I would want to hear answers to the question I posed above from the relevant experts before I would feel confident saying that.
...