2016-07-27 16:52, Hemant Agrawal: > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > 2016-07-27 13:23, Hemant Agrawal: > > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > > > 2016-07-27 15:21, Jerin Jacob: > > > > > If we agree on this then may be I can send the API deprecation > > > > > notices for rte_mempool_create for v16.11 > > > > > > > > It would have been a lot better to send a patch during the 16.07 > > > > cycle to avoid breaking again the API. > > > > I'm afraid it will even be too late for the deprecation notice. > > > > > > [Hemant] Yes! It is late. > > > we can make these changes immediately after 16.07. > > > > You cannot change the API in 16.11 without having a deprecation agreement in > > 16.07. > [Hemant] Can you still accommodate the deprecation notice for 16.07?
No, I cannot write a deprecation notice for you. And you must give some time to other developers to review your proposal and accept it. You failed to write a patch to modify the new API in 16.07 and you failed to prepare and discuss a deprecation notice for 16.11. So I think your best bet is to work now for a change in 17.02.
