Before we publish, we need to decide who is owner of the crate.
rylev
All 5 comments
As one of the owners of https://crates.io/crates/winrt, I think we can discuss whether you want to take over that crate name. From my perspective it makes no sense to develop two Rust language projections for WinRT in parallel (and also I don't have time to maintain https://github.com/contextfree/winrt-rust in a meaningful sense any longer).
I'm really happy that there is now an alternative that is supported by Microsoft directly 👍
Boddlnagg
on 30 Apr 2020
Thanks Patrick, that would be ideal. Adding @contextfree for his perspective.
Developers can make a Cargo.toml dependency using git, but it does seem like it would be a lot easier for developers to manage their version dependencies using crates.io.
kennykerr
on 30 Apr 2020
I would prefere if you could continue with the semver schema and release this project as 0.7.0.
dns2utf8
on 4 May 2020
I agree that it would be necessary to release the first version as 0.7.0 to be semver-compatible. And 7 looks almost like 1, doesn't it? 😉
Boddlnagg
on 4 May 2020
Yeah, having this project take over the winrt crate name would definitely be fine. winrt-rust was still making major breaking changes with minor versions, so I don't think having 0.7.0 be another major breaking change would be a problem?
contextfree
on 23 May 2020
Related issues
rylev
·
3Comments
Zymlex
·
3Comments
AyashiNoCeres
·
4Comments
ctaggart
·
4Comments
rylev
·
4Comments
Most helpful comment
As one of the owners of https://crates.io/crates/winrt, I think we can discuss whether you want to take over that crate name. From my perspective it makes no sense to develop two Rust language projections for WinRT in parallel (and also I don't have time to maintain https://github.com/contextfree/winrt-rust in a meaningful sense any longer).
I'm really happy that there is now an alternative that is supported by Microsoft directly 👍