merged version numbers

[saerdnaer]

Was implemented for json schedule in https://github.com/voc/schedule/commit/01a10e21e4e435dd47df0cbba45f21deee9b5f34#diff-9949c26e4143c91907d68ee62619fa15R150

Still open issue: How to merge version numbers...

[a-tze]

Version Number 1 + "-" + Version Number 2

should at least be stable /wrt to sorting. prerequisite is that input schedules (version numbers) are always processed in same order.

[saerdnaer]

Currently there is no guarantee that the version number is increased with every small little change. We also have some unversioned content as input like the self-organized session from wiki at events.ccc.de.

I personally would prefer some hash over the content or an last change date...

[a-tze]

proposal:

• hash (-part) over content replaces version numer in schedules w/o version number in them, otherwise take version number from input
• concatenation of those values results in output version number

I think this is the most transparent. Hashing inputs that have a version number are harder to track. If the resulting version is something like '0.9-ad8e39' a human can derive at least a little bit of information.

[saerdnaer]

so for the 32C3 use case, this would be 0.9-ad8e39_0.3-fefeba_abcde? (cccv frab release 0.9 + sendezentrum release 0.3 + wiki)

[a-tze]

since SZ has a version number, it should be more like '0.9-0.3-fefeba_abcde'. The idea is that sorting works, but of course it doesn't work for the hashed parts.

[saerdnaer]

was implemented this year