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

Remove CFE deprecated code for next release #815

Closed
jphickey opened this issue Aug 18, 2020 · 0 comments · Fixed by #817 or #861
Closed

Remove CFE deprecated code for next release #815

jphickey opened this issue Aug 18, 2020 · 0 comments · Fixed by #817 or #861
Assignees
Milestone

Comments

@jphickey
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Now that the "6.8.x" release branch has been created, the next release should remove all code/functions that are currently marked as deprecated.

Describe the solution you'd like
Removal of all code currently contained within an OMIT_DEPRECATED conditional compile switch.

Additional context
The removal only applies to "main" branch - not the 6.7.x release branch, where it will continue to exist for that release series. This assumes the next release (main) will become version 7.0.

There are other changes currently in development which do break some deprecated items - hence why I'd like to remove this sooner rather than later, as it saves the work of updating/fixing this old code if the intent is to remove it anyway.

Requester Info
Joseph Hickey, Vantage Systems, Inc.

@jphickey jphickey self-assigned this Aug 18, 2020
jphickey added a commit to jphickey/cFE that referenced this issue Aug 18, 2020
In the next major CFE release, this code will be no longer
supported at all.  It should be removed early in the cycle
to avoid needing to maintain this compatibility code.
@skliper skliper added this to the 7.0.0 milestone Aug 19, 2020
jphickey added a commit to jphickey/cFE that referenced this issue Aug 31, 2020
In the next major CFE release, this code will be no longer
supported at all.  It should be removed early in the cycle
to avoid needing to maintain this compatibility code.
yammajamma added a commit that referenced this issue Sep 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants