Consider tagging a new release
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 899
- PR merge metrics
- No merged PRs in 30d
Description
Hi! Distributions like e.g. Nixpkgs often use git tags and/or github releases as a cue for automated package updates. The latest OpenSfM semver tag dates to the August of 2020, and there have been many updates to OpenSfM since. I'm not familiar with OpenSfM's release schedule/policy. Would it be possible to push a new tag? Is HEAD considered stable/safe to follow?
Thanks!
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 reviewing the project's existing Git tags and GitHub releases, then determine whether HEAD is considered stable and what release policy applies. Done means a maintainer-approved release decision and, if appropriate, a new tag or GitHub release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100