All email correspondence between CMI and the MN BCA is public record. Within an email dated Jan 12, 2004, a CMI employee wrote the following:
"Keep in mind that this is not our standard procedure for releasing software. I'd much rather the software go through quality assurance procedures (test/debug) before releasing it to you. Unfortunately, you don't have the time for that"
While CMI is the only party that has access to their full source code and because of such, would be able to perform the most extensive and effective testing, in favor of speed to release vs. quality and accuracy of software, the MN BCA has CMI disregard their quality assurance procedures of testing and debugging.
Slashdot Mirror
All email correspondence between CMI and the MN BCA is public record. Within an email dated Jan 12, 2004, a CMI employee wrote the following: "Keep in mind that this is not our standard procedure for releasing software. I'd much rather the software go through quality assurance procedures (test/debug) before releasing it to you. Unfortunately, you don't have the time for that" While CMI is the only party that has access to their full source code and because of such, would be able to perform the most extensive and effective testing, in favor of speed to release vs. quality and accuracy of software, the MN BCA has CMI disregard their quality assurance procedures of testing and debugging.