please tag a release
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5k
- Forks
- 622
- Avg merge
- 8h 37m
- Merged PRs (30d)
- 5
Description
It would be nice to be able to know which version of SPTAG is the one to use in production. The traditional way to do this with git repositories is to tag one of the commits as a release. Preferably the tag would be signed with an OpenPGP key of the project maintainers.
Related issue: #110: SPTAG roadmap
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 reading the repository history and related roadmap issue #110 to determine which commit represents a production-ready version. Confirm the maintainers' OpenPGP signing process and release expectations; done means the selected commit has a signed release tag that is clearly identifiable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100