Meta-release

Fall24

API name

kyc-fill-in
GroupKnow Your Customer
RepositoryKnowYourCustomer
Target version0.2.0
Target scopeKnowYourCustomer/issues/116
Target maturityinitial
Readiness checklist

Expand

API Readiness Checklist

Checklist for kyc-fill-in 0.2.0 in release r1.3

Nr API release assets alpha release-candidate initial
public		 stable
public		 Status Comments
1 API definition M M M M Y link
2 Design guidelines from Commonalities applied O M M M Y
3 Guidelines from ICM applied O M M M Y
4 API versioning convention applied M M M M Y
5 API documentation M M M M Y Embedded documentation into API spec - link
6 User stories O O O M Y link
7 Basic API test cases & documentation O M M M Y link
8 Enhanced API test cases & documentation O O O M N
9 Test result statement O O O M N
10 API release numbering convention applied M M M M Y
11 Change log updated M M M M Y link
12 Previous public release was certified O O O M N

M3 date2024-08-12
M4 date2024-09-12
API version0.2.0
pre-release tagr1.1
M5 dateyyyy-mm-dd
public-release tagr1.3
Comments

M4': OK KnowYourCustomer r1.3 release review - Issue #95

M4: OK KnowYourCustomer r1.2 release review (M4) · Issue #85

M3: OK KnowYourCustomer r1.1 release review · Issue #68 - 

Previous API version implemented by KDDI (Japan) (source: https://www.open-gateway.com/operators-map as of 2024-08-16) 

Contacts

Toshiyasu Wakayama  Fernando Prado Cabrillo 

Additional Information

Add any other useful information about the status of the release here.

4 Comments

  1. Herbert Damker

    Toshiyasu Wakayama The target version is 0.2.0, so the title should be "kyc-fill-in v0.2.0"?

    1. 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.


      1. 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:

        • 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.  

  2. Herbert Damker

    Updated page title and target version as defined in https://github.com/camaraproject/KnowYourCustomer/pull/119