oxidecomputer / oxidecomputer/hubris
Add some non-production boards to the Hubris releases
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
It is helpful to be able to retrieve archives for dev boards that are built contemporaneously with the archives meant for customer release. While testing on production hardware is important, sometimes a dev board can help isolate a behavior.
At a minimum, grapefruit-a and -b should be added. Also consider other boards used in manufacturing and test.
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 locating the Hubris release configuration or workflow that selects boards for customer archives, then trace how existing production boards are packaged. Check how grapefruit-a and grapefruit-b are represented and identify other manufacturing or test boards built alongside releases. Done means the requested non-production board archives can be retrieved from Hubris releases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, release
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100