Hi Anatoly, > > Meeting notes for the DPDK technical board meeting > > held on 2018-10-24 > > > > Attendees: > > - Bruce Richardson > > - Ferruh Yigit > > - Hemant Agrawal > > - Jerin Jacob > > - Konstantin Ananyev > > - Maxime Coquelin > > - Olivier Matz > > - Stephen Hemminger > > - Thomas Monjalon > > > > 0) DPDK acceptance policy on un-implemented API > > - New APIs without implementation is not accepted. > > - In order to accept a new API, At minimum > > a) Need to provide an unit test case or example application > > b) If the API is about HW abstraction, at least one driver > > should be implemented. Preferably two. > > c) If there are strong objections on ML about the need > > for more than one driver for a specific API then > > the technical board can make a decision. > > - Konstantin volunteered to send existing un-implemented API > > to the mailing list. > > - The existing un-implemented APIs will be deprecated in v19.05. > > - Deprecated un-implemented API will be removed in v19.08 > > > > Does this also apply to unimplemented parts of the existing API? For > example, malloc API has long had a "name" parameter which goes > unimplemented through entire lifetime of DPDK project. It would be good > to drop this thing entirely as it's clear it's not going to be > implemented any time soon :) >
Sounds like a good idea to me. Konstantin
