oxidecomputer / oxidecomputer/progenitor
Should the crate be used with a git hash or with the published version
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
Hi,
I've been using progenitor for about a semester, and when I started, I had to set progenitor = { git = "https://github.com/oxidecomputer/progenitor" } because the published crate (around the 0.8.0 times) was not working for me.
It seems things changed quite a bit since, and there are regular releases.
So I've been wondering if I should still be using progenitor directly from the git repository, or if I should switch to the published crates (as of today) progenitor = "=0.11.0".
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
The issue names no source file, test, or entry point. Start by checking the repository's release guidance and the published 0.11.0 crate against the git dependency described here; done means the supported dependency choice is documented for users.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100