Any plans or timeline for releasing `ort` v2.0.0 stable?

[alvarobartt]

Description

Hey @decahedron1, @altunenes, and the rest of the ort team!

I'd like to ask you if there's any plan, timeline or roadmap defined upon the ort v2.0.0 stable release; if so, is that something public or that you can share?

Thanks a lot in advance, and much appreciated the work with ort 🤗

[decahedron1]

No definite timeline unfortunately, but there will at least be an rc.11 once #450 is complete.

My main concern is that there are bugs hiding in recently-added APIs that would require breaking changes to fix, and that I'd end up having to release v3.0 shortly after v2.0 because of them. (for example, #441 is looking like it would require a massive internal refactor with breaking changes)

I'd be willing to set that aside to kill off v1.x - it still gets a lot of downloads, likely due to the rc versions not being 'stable' according to Cargo and crates.io, thus they default to v1.16.3.

So the things I'd like to get done before a stable v2.0 is:

• Complete ort-web #450
• Resolve StdThread Panic while use load-dynamic and ThreadManager in Windows #441 (hopefully without breaking changes)
• More documentation & test coverage

I don't know how long that will take because I'm juggling many different projects and haven't been able to justify spending a lot of time on ort lately.

[raphaelmenges]

More documentation & test coverage

If you create an issue and list which documentation and tests could be specifically provided by the community, I would be happy to contribute. E.g., a testcase derived from the Emscripten example.

I am wondering whether the developers at onnxruntime know how great this project is integrating their library into the Rust ecosystem. I mean they have their own bindings, but these bindings seem to be rather unmaintained. ort instead makes it feel like onnxruntime is a first-class citizen of the Rust ecosystem! Did someone ever get into contact with them / Microsoft? It might be even more economical for them to stop providing their custom bindings and rather contribute here or back the project! Probably this is wish thinking, nvm 😁

[decahedron1]

MS did indeed reach out to me at one point about consolidating development! Didn't turn out, though.

I don't think I'm that worried about tests anymore; most important things are already well covered, and the rest are just various session options/things that require GPU, so not possible to add to CI.

[decahedron1]

ICYMI - I'm now tracking progress in ort 2.0.0.