oxidecomputer / oxidecomputer/maghemite
Add mechanism to automatically keep up with Omicron Dendrite and OPTE versions
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 94
- Forks
- 6
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
If the Maghemite dependencies for Dendrite and OPTE fall out of sync with Omicron, it can lead to iterop failures at runtime.
There are a number of ways to approach this. One option could be to have a dedicated branch for Omicron tracking and a reflector bot to keep common dependencies synchcornized with Omicron. I think the main branch should be able to run ahead of Omicron, and there should probably be a dependency job that keeps Maghemite mainline up to date with Dendrite and OPTE mainline.
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
No files, tests, or entry points are named. Start by locating Maghemite's dependency declarations and existing automation, then compare the dedicated-branch, reflector-bot, and dependency-job options against the Omicron, Dendrite, and OPTE mainlines. Done means Maghemite dependencies stay synchronized without preventing main from running ahead.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100