Zeeshan Ali Khan wrote:
zbus creator/maintainer here.
Thanks for weighing in.
Why annoyingly? Where else should I provide the release notes? I take the time to write proper release notes for each release so I'd appreciate some appreciation for that. :) Most projects these days don't bother at all and if they do, they just copy&paste the git log.
Firstly it's a bit hidden, I suspect most people get their releases from crates.io, click on the link to the repository when they want to view what is going on with development and don't even realise that the releases tab on the gitlab project is being used. Secondly it throws multiple crates and multiple branches in together. this can mean looking through quite a lot of entries to find the one you want. When packages bother to maintain a changelog (which sadly most don't) the convention in the rust community seems to be a file called CHANGELOG.md in the root of the source tree. > Indeed. I strongly suggest bumping directly to the latest v3. If v2 to v3 is a trivial change, then I think it does indeed make sense to skip v2. That still leaves the question of what to do about v1 to v2. My experience trying to port libslirp was that it was not a trivial task. I didn't try to port squeekboard, so maybe it was something weird about how libslirp uses the crate. I went through serveral pages of releases and found the release notes for version 2.0 but they didn't really enlighten me. > or if there's anything I can do to help. What would be helpful is persuading/helping upstreams of projects that use zbus and are currently in Debian to move to the latest version of zbus. Mainly libslirp and squeekboard.
