Changes between Initial Version and Version 1 of Ticket #294, comment 3


Ignore:
Timestamp:
11/30/2022 08:29:58 PM (4 years ago)
Author:
David Rosenberg

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #294, comment 3

    initial v1  
    11In view of Eric's comment above, the Multics software could be written so that it applied filters to the simulator version. A warning would be issued if any of the filter tests failed. I suggest the following filter tests.
    221. Byte 74 (octal) = the layout_version number, should not be NUL and should be at least some <team defined minimum>
    3 2. Byte 144 (octal) = the Release Type character, should be in a <team defined list of valid release types> or maybe should not be in a <team defined list of invalid release types
    4 3. Bytes 106‑117 (octal) = the most recent commit date, should be greater than or equal to <team defined commit date>.
    5 4. Since the release number consists of four separate fields, the test on the first three fields would have to proceed from left to right, testing that the value in a field was at least some team defined minimum. If it was '''EQUAL''' to that minimum, proceed to check the next field to the right. If it is '''GREATER''' than the minimum, then ignore fields to its right. I'm not sure whether the rightmost field (the iteration number) should be treated the same way or not. Maybe it should, or maybe any non-zero iteration number should fail the filter test.
     32. Byte 144 (octal) = the Release Type character, should be in a <team defined list of valid release types> or maybe should not be in a <team defined list of invalid release types>
     43. Bytes 106‑117 (octal) = the most recent commit date, should be greater than or equal to <team defined minimum commit date>.
     54. Since the release number consists of four separate fields, the test on the first three fields would have to proceed from left to right, testing that the value in a field was at least some team defined minimum. If it was '''EQUAL''' to that minimum, proceed to check the next field to the right. If it is '''GREATER''' than the minimum, then ignore fields to its right. I'm not sure whether the rightmost field (the iteration number) should be treated the same way or not. Maybe it should, or maybe any non-zero iteration number should fail the filter test. I would expect Development, Alpha, Beta, and Release Candidate releases to have non-zero iteration numbers, but General Releases should have a zero iteration number.