The current release manager (who is the original author but would be happy to have someone else do it) likes Duplicati version numbering plan whose main idea is (I think) that instead of the number bump done on the way to the Beta (e.g. bump at Experimental), it’s done after release that might be patched, basically opening up lots of number space. Other releases such as Canary or Nightly (not yet running) get replaced, not patched, so possibly Canary is pretty much Nightly plus a human-made release note, which people may or may not read. If you stay on Canary instead of going back to Beta per earlier note then you probably should follow Forum Releases category awhile before actually taking Canary update.
v2.0.4.1-2.0.4.1_experimental_2018-11-08
Changes in this version:
This is a collection release that is based on the 2.0.3.14 canary build.
shows previous bump-at-Experimental into 2.0.4.x range used for Beta, Beta patch, and also Canary…
The scheme might get finessed further, but to use a specific example about “Unexpected difference” fix:
v2.0.4.22-2.0.4.22_canary_2019-06-30
Fixed data corruption caused by compacting, thanks @ts678 and @warwickmm
If that had been v2.0.5.17-2.0.5.17_canary_2019-06-30, would 2.0.4.23_beta_2019-07-14 be assumed to include the 2.0.5.x fix or not? Based on number, not, but would someone rely on the date?
Above gets solved by the proposal requiring a number bump after Beta or Stable (not yet running) that might avoid getting numbers quite so mixed together (for those who look at numbers instead of dates). Experimental is currently like a pre-Beta which helps weed out update issues for infrequent updaters…
There have also been proposals around downgrade compatibility (database changes format sometimes in some Canary typically) being reflected in the version numbering, and also a proposal to admit defeat, and just do Nightly and Canary, but that seems to be a minority view. The problem is that extended user testing leading to Beta and Stable takes awhile, but it does offer a range of new-versus-better-proven… Nobody’s been keen on being fancier than a single GitHub master except maybe when releases occur.
Comments?