Custom Versioning scheme

[grd]

This proposal is about versioning scheme's. A versioning scheme is the text that a new version gets after you created the new version of a file. Versioning has been used in software and also in CAD files. Versioning needs to be flexible but specifically with CAD also requires strict rules. It also needs to be automatic, so if you have version A.1 and you want a new version you should have A.2 but that is not always the case. It could also be B.1. This means that you need to have a counter that always increases the latest version but also that the version text should not be a hard text that no one can change.

You can make versioning as good or as bad that you can think of. The default versioning scheme is good and it works. You get 1, 2, 3 etc. But there are also people that want to change that into V1, V2, V3, or 2025.01.01-1, 2025.01.01-2, 2025.01.01-3, or 1.1, 1.2, 1.3, or A.1, A.2, A.3.

This means that the version scheme needs to be flexible but with strict rules.

How can this version scheme look like? We can make a json file with the name AutoVersionNumber.json that is placed inside the directory vaults/.data/yourvault then (after this feature is implemented) it should work¹.

An example looks like this:

{
  “characters”: [
    {
      “type”: "alphabetical",
      “capitalized”: true
    },
    {
      “separator”: "."
    },
    {
      "type": "integer",
      “starts_with_zero”: false
    }
  ],
}

This generates the version number A.1, A.2, A.3, B.1, B.2 and so on.

A different example:

{
  “characters”: [
    {
      “type”: "date",
      “date_separator”: "-"
    },
    {
      “separator”: "-V"
    },
    {
      "type": "integer",
      “starts_with_zero”: false
    }
  ],
}

This generates the number 2025-01-01-V1, 2025-01-01-V2, 2025-01-01-V3, and so on.

Keywords and types

• characters list
• type ["alphabetical", "integer", "date"]
• capitalized bool
• starts_with_zero bool
• date_separator character
• separator string

What are your thoughts?

Footnotes

1. To put this file there you first need to chmod the vault and then the .data and after that the yourvault directories. Type chmod yourdir 0777 in the server ↩