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
#1
Updated by bmbouter about 2 months ago
- Parent task set to #7416
#2
Updated by daviddavis about 2 months ago
- Sprint set to Sprint 80
#3
Updated by rchan about 2 months ago
- Sprint changed from Sprint 80 to Sprint 81
#4
Updated by bmbouter about 1 month ago
- Sprint/Milestone set to 3.7.0
#5
Updated by bmbouter about 1 month ago
- Priority changed from Normal to High
#6
Updated by bmbouter about 1 month ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
#7
Updated by pulpbot about 1 month ago
- Status changed from ASSIGNED to POST
#8
Updated by rchan about 1 month ago
- Sprint changed from Sprint 81 to Sprint 82
#9
Updated by bmbouter about 1 month 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