Herbert Damker Thanks, Herbert. The target version is 0.1.0, more precisely 0.1.1. So, should I change the title to kyc-fill-in v0.1.1?
My assumption is that it is OK to have separete version number for kyc-match (v0.2.0) and kyc-fill-in (v0.1.0/0.1.1). If it is wrong, please let me know.
Yes, your assumption is correct, APIs could have different versions. That is the main reason why we did the decoupling of release numbering and API versions: the API version numbers are per API.
But, regarding the version of kyc-fill-in:
There was already a release of v0.1.1, so a new patch version must be v0.1.2
And I'm not sure if it is only a patch version, due to the change of the scope from know-your-customer:fill-in to kyc-fill-in:fill-in. Maybe v0.2.0 is more correct?
In addition the base path should now include the second digit (so /0.1-rc or /0.2-rc for the release candidate, in the public release /0.1 or /0.2) to make the initial releases distinguishable for API clients.
4 Comments
Herbert Damker
Toshiyasu Wakayama The target version is 0.2.0, so the title should be "kyc-fill-in v0.2.0"?
Toshiyasu Wakayama
Herbert Damker Thanks, Herbert. The target version is 0.1.0, more precisely 0.1.1. So, should I change the title to kyc-fill-in v0.1.1?
My assumption is that it is OK to have separete version number for kyc-match (v0.2.0) and kyc-fill-in (v0.1.0/0.1.1). If it is wrong, please let me know.
Herbert Damker
Yes, your assumption is correct, APIs could have different versions. That is the main reason why we did the decoupling of release numbering and API versions: the API version numbers are per API.
But, regarding the version of kyc-fill-in:
know-your-customer:fill-in
tokyc-fill-in:fill-in
. Maybe v0.2.0 is more correct?Herbert Damker
Updated page title and target version as defined in https://github.com/camaraproject/KnowYourCustomer/pull/119