using correct version number now for PUS C #494

Closed
muellerr wants to merge 5 commits from eive:mueller/fix-for-pus-c-version-number into development
Owner

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

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
muellerr added 1 commit 2021-10-05 12:58:36 +02:00
muellerr added this to the v2.0.1 milestone 2021-10-05 12:58:43 +02:00
muellerr added the
bug
label 2021-10-05 12:58:47 +02:00
muellerr requested review from gaisser 2021-10-05 12:59:24 +02:00
muellerr added 1 commit 2021-10-05 13:13:44 +02:00
muellerr added 1 commit 2021-10-05 13:17:21 +02:00
muellerr added 1 commit 2021-10-05 18:27:48 +02:00
muellerr added 1 commit 2021-10-09 13:36:08 +02:00
muellerr closed this pull request 2021-10-11 15:25:22 +02:00
mohr reopened this pull request 2021-10-11 15:25:50 +02:00
mohr changed target branch from development to master 2021-10-11 15:25:58 +02:00
mohr changed target branch from master to development 2021-10-11 15:26:46 +02:00
Author
Owner

Closed because this will be merged directly into master as part of #502

Closed because this will be merged directly into master as part of #502
muellerr closed this pull request 2021-10-11 15:28:46 +02:00
muellerr removed this from the v2.0.1 milestone 2021-10-11 18:03:06 +02:00

Pull request closed

Sign in to join this conversation.
No description provided.