Problem description
As we will propose OTPValidationAPI for first CAMARA meta-release we have to discuss with which public status (=maturity level).
A public status could be either initial or stable depending on the maturity level (source: API versioning - CAMARA Project - Confluence)
This decision has impact on the version:
• If the API is public but ‘initial’ as maturity level then the version will be v0.x
• If the API is public but ‘stable’ as maturity level then the version will be vX (with X>0) (so v1 for our first meta-release)
The expectation between both are distinct and can be found here.
I tend to think we're in a good situation for this API to target a stable release - so a v1.0.
There are already several live implementation (check here). our API is very mature, we had few update lately and we can manage backward compatibility ruling in future.
Problem description As we will propose OTPValidationAPI for first CAMARA meta-release we have to discuss with which public status (=maturity level).
A public status could be either initial or stable depending on the maturity level (source: API versioning - CAMARA Project - Confluence) This decision has impact on the version: • If the API is public but ‘initial’ as maturity level then the version will be v0.x • If the API is public but ‘stable’ as maturity level then the version will be vX (with X>0) (so v1 for our first meta-release)
The expectation between both are distinct and can be found here.
I tend to think we're in a good situation for this API to target a stable release - so a v1.0. There are already several live implementation (check here). our API is very mature, we had few update lately and we can manage backward compatibility ruling in future.
Expected action Get decision from the team.
Additional context cc: @hdamker