-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
gconftool2: deprecate state get #4778
gconftool2: deprecate state get #4778
Conversation
Since the new module has just been added, it's better to wait with the deprecation until much later in the 5.x.0 release cycle, or even just do it in 6.0.0. (The removal version should probably be 8.0.0 then.) I'm currently tending to do the deprecation in 6.0.0 and the removal in 8.0.0, because then we can already merge this PR into |
okie, makes sense |
Can you adjust the deprecation? Then we can merge it to main without backporting it. |
Forgot about this ticket for a while. Just done that. |
Docs Build 📝Thank you for contribution!✨ This PR has been merged and your docs changes will be incorporated when they are next published. |
@russoz thanks for doing this! |
* gconftool2: deprecate state get * added changelog fragment * Update plugins/modules/system/gconftool2.py * Update plugins/modules/system/gconftool2.py
* gconftool2: deprecate state get * added changelog fragment * Update plugins/modules/system/gconftool2.py * Update plugins/modules/system/gconftool2.py
SUMMARY
Deprecates
state=get
in favour of using modulegconftool2_info
.ISSUE TYPE
COMPONENT NAME
plugins/modules/system/gconftool2.py