cameron314 / cameron314/readerwriterqueue
Upload stable release archive
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 4.6k
- Forks
- 736
- Avg merge
- 10d 5h
- Merged PRs (30d)
- 1
Description
Hi there,
I'm working on adding readerwriterqueue as a Bazel Module to the Bazel Central Repository. My PR is here: https://github.com/bazelbuild/bazel-central-registry/pull/1088
Bazel Central Repository requires that packages point to a "Release Archive", not just a source-code archive on Github. This is because the source-code archives are automatically generated on-demand by Github, and are not guaranteed to be hash-stable.
More details here: https://github.blog/2023-02-21-update-on-the-future-stability-of-source-code-archives-and-hashes/
tldr; Please upload a static release archive of the source code for the latest release to GH
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
Review the latest readerwriterqueue release on GitHub and the linked Bazel Central Registry PR #1088 first. Confirm that a static release archive corresponding to the latest release is uploaded and available for the registry request.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100