embedded-io: API stability and 1.0.0 release

[elast0ny]

Hello, I'm working on a project that is considering using embedded-io's traits for no_std environments and had some concerns about the stability of the API.

For example, the popular postcard serde format supports embedded-io traits but only from version 0.4.0. This means that I either have to commit to an old version to use postcard or make a fork of postcard (and upstream fixes ideally).
I assume this is a decision that anyone in the no_std ecosystem has to make if they want to be generic over Read/Write.

Is there any chance that embedded-io could take a stance on backwards compatibility of its Read/Write traits (as a statement in a README perhaps) and make a release of major version 1 ?

I understand that the crate may not be in such a state to be stable "forever" but if so, it would provide much more confidence in committing to using it.