ECHNOLOGIES at Cisco)" <mgrad...@cisco.com>
> > Date: Thursday, October 5, 2017 at 4:38 AM
> > To: Ole Troan <otr...@employees.org>, vpp-dev <vpp-dev@lists.fd.io>
> > Subject: Re: [vpp-dev] API versioning
> >
> > +1
> >
> > having explicit version
le Troan <otr...@employees.org>, vpp-dev <vpp-dev@lists.fd.io>
> Subject: Re: [vpp-dev] API versioning
>
> +1
>
> having explicit version number in the api file is a good thing in my opinion.
>
> I think also Java bindings could benefit a bit from your proposa
-
PANTHEON TECHNOLOGIES at Cisco)" <mgrad...@cisco.com>
Date: Thursday, October 5, 2017 at 4:38 AM
To: Ole Troan <otr...@employees.org>, vpp-dev <vpp-dev@lists.fd.io>
Subject: Re: [vpp-dev] API versioning
+1
having explicit version number in the api file is a good thing
.
Regards,
Marek
-Original Message-
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of Ole Troan
Sent: 2 października 2017 14:37
To: vpp-dev <vpp-dev@lists.fd.io>
Subject: [vpp-dev] API versioning
All,
I have received a few suggestions that espe
All,
I have received a few suggestions that especially the dynamic language bindings
(Python, Lua) would benefit from a better versioning system than depending and
storing the CRC values of each VPP API message.
Could you please take a look at the proposal for semantic versioning of API
