Skip to content

Conversation

@os-d
Copy link
Contributor

@os-d os-d commented Sep 5, 2024

This change includes updates to align the doc with the current state of Project Mu and reflect investments moving forward.

@os-d os-d requested a review from spbrogan September 5, 2024 14:52
@makubacki
Copy link
Member

@os-d, I just noticed this PR. What's the current status?

@os-d
Copy link
Contributor Author

os-d commented Sep 19, 2024

@os-d, I just noticed this PR. What's the current status?

@makubacki, awaiting review from @spbrogan, who requested the changes. I'll reach out to him to review.

@makubacki
Copy link
Member

@os-d, I just noticed this PR. What's the current status?

@makubacki, awaiting review from @spbrogan, who requested the changes. I'll reach out to him to review.

If he confirms this meets his expectations in the ask to update, then I'll come back and look it over for a second review.

@os-d os-d force-pushed the doc_update branch 2 times, most recently from 8908e56 to bb0f78b Compare October 2, 2024 21:30
@makubacki
Copy link
Member

@os-d & @spbrogan, bumping this PR.

@os-d
Copy link
Contributor Author

os-d commented Jul 22, 2025

@spbrogan I have updated this doc now that this update is almost a year old :). Please review.

This change includes updates to align the doc with the current
state of Project Mu and reflect investments moving forward.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants