MVP hit list

[bnaecker]

Tracking issue for MVP-focused work

Current

• [x] https://github.com/oxidecomputer/opte/issues/231
• [x] https://github.com/oxidecomputer/opte/issues/10
• [x] https://github.com/oxidecomputer/opte/issues/197

Next up

• [ ] https://github.com/oxidecomputer/opte/issues/234
• [x] https://github.com/oxidecomputer/opte/issues/196
• [x] https://github.com/oxidecomputer/opte/issues/42
• [ ] https://github.com/oxidecomputer/opte/issues/61
• [x] https://github.com/oxidecomputer/opte/issues/74
• [x] https://github.com/oxidecomputer/opte/issues/160
• [ ] https://github.com/oxidecomputer/opte/issues/211
• [ ] https://github.com/oxidecomputer/opte/issues/228
• [ ] https://github.com/oxidecomputer/opte/issues/221

Blocked

• [x] https://github.com/oxidecomputer/opte/issues/236

[rzezeski]

To add some color to this issue: Ben and I were discussing OPTE work and where we should focus when we realized it would be good to have a discussion of all the current open issues and try to rank things in a way that surfaces the higher priority items without it turning into some soul-sucking agile backlog grooming task. Our idea was to kind of have a top hit list of things we are working on right now ("current") and as we complete things on that list replace them with stuff from the "next up" queue. Our general heuristic was "how bad would it be if this wasn't done for MVP"? If the answer is "bad", it's on this list.