<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-15">
<META content="MSHTML 6.00.6000.16850" name=GENERATOR></HEAD>
<BODY style="MARGIN: 4px 4px 1px">
<DIV>Olaf:</DIV>
<DIV> </DIV>
<DIV>I have read thru the "Release Notes CM3 5.8.2" page and the "CM3 Release Candidate Index" page. Great job putting this together!</DIV>
<DIV> </DIV>
<DIV>Here are some comments for your consideration:</DIV>
<DIV> </DIV>
<DIV>1. The section on "Package", particularly the first paragraph, I think is a bit confusing. The CM3IDE documentation includes a lot of information on packages, so perhaps the missing link in this section should reference that documentation. To me, a package is a set of sources that together represent one compilation unit for the purpose of building a library, program, or other assemblage of information (e.g., documentation). Each package resides in a directory (folder), with sources and generated files in subdirectories (sub folders) of the package's folder. In the top-level CM3 source tree, packages are grouped into categories, with each category represented by a subfolder rooted in that top-level, and the packages comprising each category rooted in the category's folder.</DIV>
<DIV> </DIV>
<DIV>2. I presume that we do intend to make NT386 available for this release, even though it says "Not Available Yet".</DIV>
<DIV> </DIV>
<DIV>3. I find the "-bin-min-" and "-bin-core-" terminology a bit confusing. To me, the "core" of something is the "heart" or "minimal" part of it. Would it make more sense to rename "-bin-core-" to "-bin-std-"? Indeed the explanation given for "core" says in one place that it represents a "standard" installation. In another place it is called "package pool". Also, "min" in one place is called the "central installation hierarchy". Suggest we be consistent. To me it makes more sense to have "min" represent the "minimal installation" and "std" the "standard installation" and "all" represents "everything."</DIV>
<DIV> </DIV>
<DIV>4. I don't understand the "-bin-ws-" concept of "precompiled user workspace" and how it would be useful. Please elaborate.</DIV>
<DIV> </DIV>
<DIV>5. All of the instructions seem to apply for UNIX-like environments. We need to augment these to include how to do it on non-Unix environments, such as Windows. For the scripts, like "install.sh", do we intend to provide Windows command/batch files, e.g. "install.cmd" or "install.bat"?</DIV>
<DIV> </DIV>
<DIV>6. When we finally settle on a release name, need to update the names in these instructions, e.g., replace "d5.8.1-RC1" under "Installation Procedure", and "RC1" in other places.</DIV>
<DIV> </DIV>
<DIV>7. "Installation Procedure" step #5, change "shop" to "ship".</DIV>
<DIV> </DIV>
<DIV>8. "In case of problems" step #4, last line, change "volunteers" to "volunteer" and change "his" to "his/her".</DIV>
<DIV> </DIV>
<DIV>Hope some of this helps.</DIV>
<DIV> </DIV>
<DIV>Thanks for all your work on this!!!</DIV>
<DIV> </DIV>
<DIV>Regards,</DIV>
<DIV>Randy Coleburn</DIV></BODY></HTML>