using correct version number now for PUS C #494
No reviewers
Labels
No Label
API Change
Breaking API Change
bug
build
cosmetics
Documentation
duplicate
feature
help wanted
hotfix
invalid
question
Refactor
Tests
wontfix
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: fsfw/fsfw#494
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "eive:mueller/fix-for-pus-c-version-number"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When writing unittests for the Python spacepackets package, I found the bug that the FSFW PUS C TM implementation still uses the wrong version number.
This was not caught because the previous client application still expected one.
This is an important bugfix and should go into Revision v2.0.1
Closed because this will be merged directly into master as part of #502
Pull request closed