Project

Profile

Help

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 over 4 years ago. Updated about 4 years ago.

Status:
CLOSED - CURRENTRELEASE
Priority:
High
Assignee:
Category:
-
Sprint/Milestone:
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 #1

Updated by bmbouter over 4 years ago

  • Parent issue set to #7416
Actions #2

Updated by daviddavis over 4 years ago

  • Sprint set to Sprint 80
Actions #3

Updated by rchan over 4 years ago

  • Sprint changed from Sprint 80 to Sprint 81
Actions #4

Updated by bmbouter over 4 years ago

  • Sprint/Milestone set to 3.7.0
Actions #5

Updated by bmbouter over 4 years ago

  • Priority changed from Normal to High
Actions #6

Updated by bmbouter over 4 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to bmbouter
Actions #7

Updated by pulpbot over 4 years ago

  • Status changed from ASSIGNED to POST
Actions #8

Updated by rchan over 4 years ago

  • Sprint changed from Sprint 81 to Sprint 82

Added by bmbouter over 4 years ago

Revision 374af38f | View on GitHub

Add deprecation policy to plugin writer guide

  • Adds docs on how the deprecation process works
  • Adds docs on how to depend on pulpcore with this policy

closes #7413

Actions #9

Updated by bmbouter over 4 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100
Actions #10

Updated by pulpbot about 4 years ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Also available in: Atom PDF