Skip to content
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

CFE_MISSION_REV defined in 2 locations #877

Closed
skliper opened this issue Sep 10, 2020 · 5 comments · Fixed by #1084 or #1109
Closed

CFE_MISSION_REV defined in 2 locations #877

skliper opened this issue Sep 10, 2020 · 5 comments · Fixed by #1084 or #1109
Labels
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Sep 10, 2020

Describe the bug
CFE_MISSION_REVE defined in 2 locations

To Reproduce
Inspection

Expected behavior
Define in 1 location... if it's for clone and own, version seems to make sense... if it includes configuration versioning then useful in the config file.

Code snips

#define CFE_MISSION_REV 0

#define CFE_MISSION_REV 0 /*!< @brief ONLY USED by MISSION Implementations. Mission revision */

System observed on:
N/A

Additional context
None

Reporter Info
Jacob Hageman - NASA/GSFC

@skliper skliper added the CCB:Ready Ready for discussion at the Configuration Control Board (CCB) label Sep 11, 2020
@skliper
Copy link
Contributor Author

skliper commented Sep 11, 2020

Need a decision on resolution approach.

@skliper skliper added this to the 7.0.0 milestone Sep 11, 2020
@skliper skliper added the bug label Sep 11, 2020
@jphickey
Copy link
Contributor

FWIW I don't think either of these are correct - it should be in cfe_mission_cfg.h ...

I think the one in cpu1_platform_cfg.h is probably a mistake ... that file is only supposed to be platform stuff, not mission stuff. And missions shouldn't be changing stuff directly in the CFE source code.

@astrogeco
Copy link
Contributor

astrogeco commented Sep 15, 2020

I support removing it from version.h we'd need to apply this to all components though.

@skliper
Copy link
Contributor Author

skliper commented Sep 21, 2020

If they are changing it though, most likely it's due to changing CFE source code already so I don't have a strong objection to just leaving it in the header file... It's for the clone-and-own types, not really intended for configuration versioning as far as I can tell. If it was configuration versioning, I'd expect it to be platform specific...

@skliper
Copy link
Contributor Author

skliper commented Sep 23, 2020

CCB 2020-09-23: remove from the config, treat this as the number that "projects" get to update as the version number. Leave in version.h got at least 2 votes.

@yammajamma yammajamma added CCB-20200923 and removed CCB:Ready Ready for discussion at the Configuration Control Board (CCB) labels Sep 23, 2020
skliper added a commit to skliper/cFE that referenced this issue Jan 11, 2021
astrogeco added a commit that referenced this issue Jan 25, 2021
…em_all

Fix #877, Remove duplicate CFE_MISSION_REV define
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
4 participants