On Wed, Jan 03, 2018 at 09:17:32AM +0100, Maxime Coquelin wrote: > >>Reviewed-by: Maxime Coquelin <maxime.coque...@redhat.com> > > > > From 3.2. Managing ABI updates, General Guidelines: > > > > New APIs will be marked as experimental for at least one release to > > allow any issues found by users of the new API to be fixed quickly. > > > >http://dpdk.org/doc/guides/contributing/versioning.html > > > >I'm new to DPDK so I followed this guideline strictly and expect the > >maintainers to mark the API stable at some point in the future when they > >are happy with it. Maybe this guideline isn't followed strictly for > >librte_vhost? > > Thanks for the pointer, it seems it is not strictly followed for > librte_vhost & other libs. Let's keep it experimental for the coming > release.
IIRC, it's a new guideline added recently (people were talking about that in last year's DPDK user event after all). And my understanding is, for a new (big set of) APIs, it's good to make them experimental, as normally, it's not an easy task to make a big stuff right in one time. For this one, which is simple and straightforward, I don't see a strong need to mark it as experimental. Thus I have removed it (while apply). If anyone has objections, let me know. Thanks. --yliu