What is the future of Detours' versioning plans?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 6.4k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
The last and only release tag for Detours was created in 2016 - 9 years ago - and hasn't been updated since. This is the REF tag that vcpkg uses for Detours. On top of many changes & improvements being made since then, I can't even get arm64 to work locally using the 4.0.1 release. Is it safe to say that this release should be left behind in the dust and that package managers such as vcpkg should be updated to use a commit off main?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the 4.0.1 release tag with the current main branch and reviewing how vcpkg references Detours. The issue is complete only when maintainers agree on a versioning or release target and the relevant package-manager reference is updated; the payload names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100