NFD

I don't think a semver-inspired MAJ.MIN.PATCH versioning scheme is appropriate for a project like ndn-tools which is a collection of command-line programs. In our past releases, we've kept MAJ==0 and bumped either MIN or PATCH pretty arbitrarily, while almost all releases contained a mix of bug fixes and new (or improved) features.

I propose switching to a simpler scheme, either just a single version number or a time-based version (plus an optional patch component). For example:

• single number: VV(.PP), e.g. v1, v2, ..., v245... like systemd or GCC.
• time based: YY.MM(.PP) or YY.SS(.PP), e.g. 21.10, 17.04, 22.1, ... like DPDK, Ubuntu, or mesa. The middle number can be either the month (MM) or a sequential number (SS) that resets to 1 whenever the year changes.

In both cases an optional patch component (PP) can be appended, this is reserved for purely bug-fix releases, e.g., a hotfix for a critical bug. Given our history, at least in ndn-tools this component will almost always be zero (or omitted altogether).