implement (semantic) versioning

[zachll]

goals

• KB is versioned (semantic versioning is useful)
• Version of KB used in PFP is captures and easily discovered
• Version of the KB is regularly and sensibly updated
• localizations are versioned in a way that makes it clear they are different from but related to to general KB

Q&A

• What is in main that is not should not be used for the MPOG trial? Nothing
• Does everything in main work? No
• How about measures and default preferences (and other localizations)? Don't know yet
• Where should the version be used? This can be in the output messages, logs, a separate /info endpoint
• How should the version be set? We want to make this as automatic as possible; built into our workflow. For now we can manual set a version

[zachll]

• implement changelog
• setup initial release

[zachll]

Problem: The knowledge base has not been organized to specify which version will be used in the trial, as compared with the larger set of content that is available to use Versioning needs to support projects in differentiating selected content from the more general set