#3 Tag the recent data changes

One option could be to use https://calver.org/

how's `YYYY.0M.MICRO`? we don't tend to update by day, hence the `MICRO` would be more informative. plus, sometimes (e.g. at the beginning of this repo), there could be multiple tags in a day, hence `MICRO` seems more informative than `0D`. if we want to rename tags, this is the resulting suggestion, based on that: | old tag | new tag | notes | | --- | --- | --- | | NA | `2023.11.1` | remove mandatory suffices from config files | | `reorg` | `2023.10.3` | move subfolders from data on top | | `trimmed` | `2023.10.2` | keep only trimmed data, remove full data | | `orig` | `2023.10.1` | original data (trim + full) transfered from Gitlab | I can create a changelog based on this table