On Mon, Jul 12, 2021 at 11:08 PM Ben Hutchings <ben.hutchings@xxxxxxxxxxxxx> wrote: > > I'm working on a project that requires GPIO debouncing and is planned > to use libgpiod. But debouncing is only available on the unreleased > next/libgpiod-2.0 branch. > > What we'd like to know is whether the current C API on that branch is > expected to change much before release. I don't expect any commitment > to API or ABI stability, but it would be helpful to have some > indication of how much change is likely to be needed in a client that > is written for the current API. > > Thanks, > > Ben. > Hi Ben! While - as you already assumed - there are no commitments to any API & ABI stability yet, the interface should not change very much. I have a single set of API changes in my queue that we discussed while reviewing the C++ bindings and I don't expect there to be many more coming after that. Again: this is an estimation, not a promise. Best Regards Bartosz