oxidecomputer / oxidecomputer/omicron
Include `humility` in the switch zone?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
For similar reasoning to #6153, it would smooth over some support operator wrinkles to ship humility in the switch zone. This is a little trickier than faux-mgs from a versioning point of view; we might very well want a humility that's newer than whatever the latest was when a release was cut, but I think most of the time "humility as of the release" would probably be fine?
This probably depends on https://github.com/oxidecomputer/humility/issues/421.
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 reading the related issue #6153 and the blocking humility issue #421, then inspect how the switch zone packages versioned components. Clarify whether the release should include humility as of the cut or track a newer version; done means the packaging and versioning policy are agreed and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100