Task #5184
closedChange versioning scheme
100%
Description
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)
orYY.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).
Updated by Alex Afanasyev about 3 years ago
Call on 2021-11-12 decided to change versioning scheme for NFD and ndn-tools to time based format YY.MM(.PP)
, but keep semantical versioning for libraries (ndn-cxx).
Updated by Davide Pesavento about 3 years ago
- Project changed from ndn-tools to NFD
- Category set to Build
Updated by Davide Pesavento almost 3 years ago
- Blocks Task #5172: Release NFD 22.02 / ndn-cxx 0.8.0 added
Updated by Davide Pesavento almost 3 years ago
- Status changed from New to In Progress
Updated by Davide Pesavento almost 3 years ago
- Status changed from In Progress to Code review
- Assignee changed from Davide Pesavento to Alex Afanasyev
- % Done changed from 0 to 80
Updated by Davide Pesavento over 2 years ago
- Status changed from Code review to Closed
- % Done changed from 80 to 100