Task #2003
closed
StatusServer: include NFD version in NfdVersion field
100%
Description
In StatusServer, include software version in NfdVersion field as part of returned packet.
Spec: ForwarderStatus
This Task includes a backwards-incompatible change in ndn-cxx ndn::nfd::ForwarderStatus type.
In the future, there MAY be a configure option to hide the exact version number and show a less-specific version.
The design should permit this possibility.
Updated by Junxiao Shi about 10 years ago
- Blocked by Task #2002: ForwarderStatus: include software version in NfdVersion field added
Updated by Junxiao Shi about 10 years ago
- Blocks Task #1916: nfd-status: display NFD version added
Updated by Junxiao Shi about 10 years ago
- Subject changed from StatusServer: include SoftwareVersion to StatusServer: include NFD version in NfdVersion field
- Description updated (diff)
Updated by Junxiao Shi about 10 years ago
- Related to Task #2004: Ensure software version string conforms to Semantic Versioning added
Updated by Junxiao Shi about 10 years ago
- Assignee set to Hila Ben Abraham
20141112 conference call approves to make a backwards-compatible change.
Updated by Hila Ben Abraham about 10 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
Updated by Hila Ben Abraham about 10 years ago
If I understand correctly, the purpose of tasks #2003 and #1916 is to modify the current nfdVersion field in StatusServer to present NFD_VERSION_BUILD_STRING instead of NFD_VERSION. Am I right? Is this what you mean by 'software version'?
There is a long discussion in #1916 regarding the required version format, but I couldn't understand the final decision.
Updated by Junxiao Shi about 10 years ago
From spec:
NfdVersion: usually same as
nfd --versionoutput
So this shall be NFD_VERSION_BUILD_STRING.
Updated by Hila Ben Abraham about 10 years ago
- Status changed from In Progress to Code review
Updated by Junxiao Shi about 10 years ago
- Status changed from Code review to Closed