-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[nasa/nos3#555] basic FSW dev plan,Some diagrams still needed called … #567
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## dev #567 +/- ##
=======================================
Coverage 72.77% 72.77%
=======================================
Files 744 744
Lines 91183 91183
Branches 6923 6923
=======================================
Hits 66362 66362
Misses 24821 24821 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good other than the TODOs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great minus the TODOs.
Created a FSW Dev plan in Markdown. To verify, please review the md file called STF_FSW_Development_Plan.md
If you have any additions, or feedback please feel free to edit.
There are 3 todo's for a couple tables and diagram we may want to create. We can create issues after the initial merge. What I am looking fore here is if the Sections defined and described adequately describe the STF mission.
possible issues to create:
This merge closes #555
no submodules need to be merged