You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current versioning system could benefit from incrementing the Build Baseline after each release candidate, setting the Revision to 0 (instead of 99), and replacing the Version String with the Build Baseline/Codename.
Describe the solution you'd like
Build Baseline is incremented after each release candidate (it would be set to "equuleus-rc1" at the time of this issue)
Mission Revision is set to to 00
Addition of a Current Development Cycle Codename #define
Version String is removed, and all references to it replaced with the Build Baseline/Codename
Describe alternatives you've considered
The current system. It has some shortcomings, however, in that the build baseline is incremented very infrequently (which confuses users).
Requester Info
Dylan Z. Baker/ NASA GSFC
The text was updated successfully, but these errors were encountered:
dzbaker
added a commit
to dzbaker/cFS-GroundSystem
that referenced
this issue
Dec 26, 2023
Is your feature request related to a problem? Please describe.
The current versioning system could benefit from incrementing the Build Baseline after each release candidate, setting the Revision to 0 (instead of 99), and replacing the Version String with the Build Baseline/Codename.
Describe the solution you'd like
Describe alternatives you've considered
The current system. It has some shortcomings, however, in that the build baseline is incremented very infrequently (which confuses users).
Requester Info
Dylan Z. Baker/ NASA GSFC
The text was updated successfully, but these errors were encountered: