freifunk-berlin / firmware

DEPRECATED: Build system for Berlin firmware. Please user the pinned falter-repos instead
https://berlin.freifunk.net
GNU General Public License v3.0
74 stars 34 forks source link

change versioning scheme to based on release date #747

Open SvenRoederer opened 4 years ago

SvenRoederer commented 4 years ago

Some points should make us think of changing the current versioning-scheme.

I vote for going to something like "Freifunk Berlin 2020.02.0" for a release scheduled for early 2020. Consequently the 1st maintenance-release will become "Freifunk Berlin 2020.02.1" and a prerelease will be "Freifunk Berlin 2020.02.0-rc1". This will not strictly meet the SemVer-definition, as we will change the major-number on a annual basis, even if there are no incompatible API changes.

everloop2 commented 4 years ago

numbers: appreciate it. Its far more easy to compare.

znrR commented 4 years ago

Pro Nickname: "Marketing" because we can dedicate a major release to an "influentual" person such as Hedy Lamar, User Benefit of easily rememberable major releases (human language readable)

Con Nickname: The field to store that nickname has been removed by OWRT and it would mean we need to attach it to some other field (eg. vendor) which requires follow up work on various currently unknown non firmware related projects to hide that information again.

znrR commented 4 years ago

proposal: could also be placed in the footer and no longer be part of the "real" version number as show in screenshot Screenshot 2020-04-21 at 20 59 02

znrR commented 4 years ago

technically this would look like: $CONFIG_VERSION_DIST Firmware Release $CONFIG_VERSION_FFCODENAME $CONFIG_VERSION_DEDICATION

znrR commented 4 years ago

also we agreed on changing the versioning from a consecutive 1.1.XX to timestamp based 2020.XX.Y which is similar to the OWRT scheme and keeping SemVer numbering.