Project

Profile

Help

Actions
Send by e-mail Copy link

Story #7413

closed

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

Added by bmbouter about 4 years ago. Updated about 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
bmbouter
Category:
-
Sprint/Milestone:
3.7.0
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 DeprecationWarnings at runtime and then removed in the following pulpcore release.
Actions
Send by e-mail Copy link

Also available in: Atom PDF