Story #7413
Story #7416: [Epic] As a plugin user, I can use the next verison of pulpcore without upgrading my plugin
As a plugin writer, I enjoy a 1-release depcrecation cycle
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation
Sprint:
Sprint 82
Quarter:
Description
Background¶
https://www.redhat.com/archives/pulp-dev/2020-August/msg00065.html
To Do¶
This is an all-documentation story. The following should be done:
- Update these docs with recommend single-version pinning. The new docs should recommended pinning to include two pulpcore versions. So if you plugin is being released to be compatible with pulpcore 3.7 it would be
pulpcore>=3.7,<3.9. - Add new section to the docs on [this page] that call out the pulpcore.plugin 1-cycle depcreation policy. This should indicate that first removals will be deprecated for one release and show their users
DeprecationWarningsat runtime and then removed in the following pulpcore release.
Associated revisions
History
#2
Updated by daviddavis 10 months ago
- Sprint set to Sprint 80
#9
Updated by bmbouter 9 months ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|374af38fdc26a3181ad696466087ed9e6d8f943a.
Please register to edit this issue
.
Add deprecation policy to plugin writer guide
closes #7413