openhcl: Track outstanding servicing state mesh ids that are not finalized
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Rust
- Stars
- 1.9k
- Forks
- 238
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 100
Description
I'm not sure we have anything in particular. I think we need to be vigilant/add it to our release checklist though.
Or perhaps we should take the stance that these must have corresponding GH issues in the comment?
Originally posted by @chris-oo in https://github.com/microsoft/openvmm/pull/450#discussion_r1881145924
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
Start with the discussion in microsoft/openvmm#450, especially the comment linked in this issue, to understand the outstanding servicing state mesh IDs concern. Clarify with maintainers whether the expected outcome is a release-checklist item, tracking mechanism, or GitHub issue links. Done should be an agreed process for identifying and recording IDs that are not finalized.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100