Hi all, The ikev2 plugin is currently getting some much needed love [1] [2] but it also means that its API is starting to show its age. We'd like to mark it as "In-Progress" under the new API change process [3] so that we can quickly improve it. The rationale is: - the requirement for an API to transition to "In-Production" is for the API to be stable and *tested* - there are currently no ikev2 unit test at all, and in fact the 1st proposed API change was motivated by the introduction of the initial test cases [4] - we are not aware of any users of the ikev2 plugin API today apart from the Calico-VPP integration
Of course, a possibility would be to deprecate the existing one and to introduce a new one as "In-Progress" at the expense of more work. What does the community think here? Thanks ben [1] https://jira.fd.io/browse/VPP-1889 [2] https://jira.fd.io/browse/VPP-1904 [3] https://wiki.fd.io/view/VPP/ApiChangeProcess [4] https://gerrit.fd.io/r/c/vpp/+/27536
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#16741): https://lists.fd.io/g/vpp-dev/message/16741 Mute This Topic: https://lists.fd.io/mt/74919923/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
