[FEA] Semantic versioning
Open
Nobody has claimed this yet.
P3: Backlog
type: feature request
- Dominant language
- Cuda
- Stars
- 667
- Forks
- 120
- Avg merge
- 7d 5h
- Merged PRs (30d)
- 4
Description
How do we want to employ semantic versioning for this library?
Thrust for instance updates the release version by hand by setting new values in thrust/version.h.
This is required if we opt for versioned inline namespaces to solve #189.
Contributor guide
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 reading the semantic-versioning question and the linked Thrust version.h example, then review issue #189 to understand why versioned inline namespaces matter. The issue needs a decided versioning approach and a documented way to update release values before implementation can be considered done.
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