open-telemetry / open-telemetry/opentelemetry-cpp-contrib
Releases, versioning
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 153
- Forks
- 184
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 26
Description
How should we release different contrib projects?
nginx now (#10) builds release binaries for different platforms and I'd like expose these artifacts via Github releases.
Should each project have it's own version tag? E.g. nginx-0.1.0 and httpd-0.1.0 so when the tag is created a GH release will be available.
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 nginx release-binary setup referenced in issue #10 and how the contrib projects are currently tagged. Define and document a per-project versioning and GitHub Releases approach, including how platform artifacts are exposed. Done means the convention is agreed and its release workflow is specified for the different contrib projects.
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
- Mostly clear
- Newbie friendliness
- 25/100