Plans to create a new release?

[autoantwort]

Currently the build of corrade is broken in vcpkg (microsoft/vcpkg#45091). The errors are fixed on the master branch, but there is no new release since years. Should vcpkg switch to a "rolling" release where every master commit is a releaseable version or are there plans to create a new release?

[mosra]

It's planned (tracked in mosra/magnum#453), but the project roadmap is driven by needs of its main users, who are also funding the development. They generally rely on latest master (which is kept stable at all times) for best turnaround times and so they don't really need/want me to spend extra time with version management, which means it's all left to be done in my spare time once everything else is done and so it progresses very very slow.

To make a tagged release where I can present new features, I first need to make those features sufficiently complete & documented, which takes time. And, OTOH, "just tagging some commit" as v2025.04 without doing corresponding announcements and feature advertising and such would be wasted opportunity.

I don't have a good answer, sorry. I'm always directing vcpkg users to use --head (because the version from 2020 is basically irrelevant five years later), but upgrading those is a pain because one has to explicitly update --head of every dependency first, in correct order. If somehow vcpkg could default to --head and make updates of such installs easier, that'd be a way.