Thanks for keeping this up, Will. This sounds reasonable to me at least.
I think stable API was more of a concern with C where it would (and did) get
bound into multiple languages, multiple implementations, etc. and evolving the
API is much more difficult in the first place. Hopefully Rust, Go,
I've been thinking about the process here, and I'd like to propose an
alternate path. As I understand it, currently the process is:
1. Approve the Rust API as a stable API
2. "Release" Rust API as part of a new version of the ADBC format
3. Release Rust libraries in tandem with other ADBC librarie
