Dataplane Contract Design: Versioning

[kylebrandt]

The contract will need versioning in order to be able to handle changes going forward, and identify when we are in the contract from the start.

Outcomes:

• Minimal: We need a version somewhere for consumers to switch on to know if they are in the dataplane contract.
• We picked the right scope of what to version (Whole contract, per kind, per datatype (kind+format))
• We decide where the version will live
• We articulate what promises come with major versions
• We have an idea of how to tie version to the spec
• We have an idea of how to tie the version to the sdk library code
• Design doc that researches and poses these questions
• Version property is merged into SDK code
• We have some story in terms of consumers and producers as to what happens when there is versio change - how to devs handle it?

Notes:

• Versioning will be Major.Minor style (no patch) - scheumata style

[kylebrandt]

On @kylebrandt - Get D Doc Started