-
Key: C2MS11-190
-
Status: closed
-
Source: Kratos RT Logic, Inc. ( Mr. Mike Anderson)
-
Summary:
This is one for C2MS 2.0. Capturing it here, because this is the only avenue to enter issues at present.
Instead of a F32 for version number, which then uses a year, like 2024.0, we should change this to a formatted string that uses Semantic Versioning, with a string that looks like the following:
MAJOR.MINOR.PATCH
Examples: "2.0.0", "2.1.1"
Note that this means changing the base type and the meaning of the current version numbers.
Note, too, that this shouldn't simply be type STRING, but should be something like VERSION-STR with the format defined by C2MS.
Also, consider getting rid of the separate header version and message content version. This is just something to bring up to the group.
-
Reported: C2MS 1.0 — Wed, 27 Sep 2023 19:53 GMT
-
Disposition: Deferred — C2MS 1.1b1
-
Disposition Summary:
defer to a later 2.0 release
Defer
-
Updated: Mon, 16 Sep 2024 14:18 GMT
C2MS11 — Use Semantic Versioning for Version Number of Messages
- Key: C2MS11-190
- OMG Task Force: Command and Control Message Specification (C2MS) 1.1 RTF