Stable release

[KnorpelSenf]

The crate currently only provides 0.x releases. The README also states that semantic versioning is used, but semantic versioning defines all 0.x releases as pre-releases that may have arbitrary breaking changes even between patch versions.

What is needed to bring this crate to a first stable version?

Is there any way for me to help you get there faster?

[pascalkuthe]

imara-diff uses the more common colloquial meaning of semantic versioning that is common in rust where 0.1.0 -> 0.2.0 is a breaking change but 0.1.0->0.1.1 is not so I don't see it as too urgent (and if you want to be super strict about it the all our dependencies would have to be 1.0 aswell and libraries like hashbrown which are around way longer and are more mature still aren't at 1.0 and likely wont' be soon). Probably we can do 1.0 soonish. 0.2.0 had the major API changes I wanted so I don't expect too many breaking changes but want to get some more time to polish and for dust to settle (and for gitoxide to migrate to 0.2 and see the posprocessing in action there to make sure the new API works for those usecases @Byron)

[KnorpelSenf]

Alright, understood. Just wanted to make sure this isn't a case of https://0ver.org.

[Byron]

Thanks for addressing this. I also am not in a rush for a 1.0, but also won't mind to at some point say: that's it :). It's good, we keep it as is and no major changes are needed anymore. Until then, let's be sure we don't run into the 'inflato-ver problem' where crates go 1.0 too early and then can't keep their stability promise (the example here comes from tooling around the publishing process which can't ensure downstream is stable if any of its dependencies has a breaking change).