> Yeah, i would rather not mark all api in progress since that would make
> the transition much longer.
Agreed.
> So I suggest a 1 month period during a developer that wants to downgrade
> an API, prepares a change with *just that action*, clearly marked “API
> downgrade”, type: fix, adds me as
> Personally, I think it would be a good idea to mark ALL APIs as In-Progress,
> as it matches the (lack of) guarantees in previous releases,
> and let maintainers mark some messages as Production on their own pace.
I'm not sure how you could reconcile that with e.g. the CRC job verifier nor
all
-
From: vpp-dev@lists.fd.io On Behalf Of Benoit Ganne
(bganne) via lists.fd.io
Sent: Tuesday, 2020-June-16 18:29
To: vpp-dev@lists.fd.io
Cc: Filip Tehlar -X (ftehlar - PANTHEON TECH SRO at Cisco) ;
Andrew Yourtchenko (ayourtch)
Subject: [vpp-dev] ikev2 API & new API change process
Hi a
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
