Remove deprecated code (release candidate prep) #770
Comments
|
@astrogeco @jphickey Should we make a pre-removal tag, then do this to clean up for the code review? Not critical, but we need to pick some point prior to release. |
skliper
added a commit
to skliper/osal
that referenced
this issue
Feb 17, 2021
astrogeco
added a commit
that referenced
this issue
Feb 26, 2021
Fix #770, Remove deprecated elements
jphickey
pushed a commit
to jphickey/osal
that referenced
this issue
Aug 10, 2022
Update Version Numbers description to remove statement on Revision number increases with development build Add description for build name and build number. Add buildnumber macro Add CFE_VERSION Add CFE_VERSION_STRING macro Use CFE_VERSION to event messages for different services Check for OSAL_VERSION and CFE_PSP_VERSION macros and populate them with version numbers if they don't exist. Add CFS_VERSIONS macro Use new version string in event messages Use new macros in evs and tbl startup events
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
OSAL_OMIT_DEPRECATEDelements exist to help with upgrade/transition and reduce frequency of breakage.Describe the solution you'd like
Remove deprecated code for major release.
Describe alternatives you've considered
Could tag before removal for any user that would benefit from a "gentle" transition.
Additional context
None
Requester Info
Jacob Hageman - NASA/GSFC
The text was updated successfully, but these errors were encountered: